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 2376-2400 of 2475 flagged pages
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, including certificate creation and secret encryption. However, Windows-specific tools (PowerShell, Windows Defender, Azure DSC) are often mentioned first or exclusively, and Windows examples (PowerShell commands) are presented before Linux equivalents. Some sections (Windows Defender, Windows security baselines) are Windows-only, but these are clearly marked and do not impact Linux users. Overall, Linux parity is good, but Windows bias is evident in ordering and tool references.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their ordering to avoid Windows-first bias.
- Where possible, mention Linux equivalents (e.g., for Azure DSC, reference Ansible or other Linux configuration tools).
- Clarify when a section is Windows-only and provide links to Linux alternatives if available.
- Expand Linux-specific guidance where possible, such as recommended Linux security baselines or antivirus solutions.
- Ensure PowerShell and Windows tool references are balanced with Linux command-line and tool examples.
Create Pull Request
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml under <WindowsServer>) is consistently presented first, and PowerShell examples are included for service creation and updates without Linux CLI or script equivalents. There is a mild bias toward Windows tools and patterns, but Linux/standalone parity is generally maintained via JSON examples and explanations.
Recommendations
- Add Linux CLI (e.g., Bash, Azure CLI) examples for service creation and updates alongside PowerShell examples.
- Clarify that PowerShell commands can be run on Linux via PowerShell Core, or provide equivalent commands using cross-platform tools.
- Consider presenting cross-platform (ClusterConfig.json) examples before or alongside Windows-specific (ClusterManifest.xml) examples.
- Explicitly mention Linux/macOS support for standalone Service Fabric clusters where relevant.
Service Fabric
Package an existing executable to Azure Service Fabric
...abric/service-fabric-guest-executables-introduction.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. The directory structure example uses a Windows-style .exe file (existingapp.exe), and the schema definition path is given only in Windows format (C:\Program Files\Microsoft SDKs\Service Fabric\schemas\ServiceFabricServiceModel.xsd). There are references to Visual Studio as a packaging tool, but no mention of Linux/macOS equivalents or cross-platform CLI tools. No Linux/macOS-specific examples or file paths are provided.
Recommendations
- Add examples using Linux/macOS file paths and executable formats (e.g., existingapp, not just existingapp.exe).
- Mention cross-platform tools or CLI alternatives to Visual Studio for packaging and deploying guest executables.
- Provide information about where schema files are located on Linux/macOS, if available.
- Include sample directory structures and manifest file references using Linux/macOS conventions.
- Clarify if Service Fabric SDK and guest executable packaging are supported on Linux/macOS, and provide guidance if so.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, there is a slight bias in mentioning Windows container runtimes and tools in more detail, and Windows scenarios (such as IIS lift-and-shift) are described before Linux equivalents. Windows tutorials and links are sometimes listed before Linux ones, and Windows-specific tools (Mirantis Container Runtime, DockerEE) are highlighted, while Linux only mentions Docker generically.
Recommendations
- Ensure Linux and Windows tutorials/examples are presented together or alternate their order to avoid 'windows_first' bias.
- Expand Linux-specific scenarios and examples, such as using NGINX or other common Linux workloads, to match the detail given to Windows/IIS scenarios.
- Mention Linux container runtimes and tools (e.g., containerd, Podman) if relevant, not just Docker.
- Provide parity in describing container isolation mechanisms for Linux (cgroups, namespaces) alongside Windows/Hyper-V explanations.
- Add links to Linux container documentation and quickstarts with equal prominence as Windows links.
Service Fabric
Service communication with the ASP.NET Core
...vice-fabric-reliable-services-communication-aspnetcore.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides comprehensive guidance for both Kestrel (cross-platform) and HTTP.sys (Windows-only) web servers in Service Fabric Reliable Services. While Kestrel is recommended and well-documented for cross-platform (Linux/Windows) scenarios, HTTP.sys (a Windows-only technology) is also described in detail, with its limitations on non-Windows platforms clearly stated. In some sections, Windows-specific tools and patterns (such as HTTP.sys and netsh) are mentioned before their Linux equivalents or alternatives, and Windows-specific configuration is sometimes described first. However, the documentation does not omit Linux support and generally recommends Kestrel for cross-platform use.
Recommendations
- When introducing HTTP.sys, explicitly state up front that it is Windows-only and direct Linux/macOS users to Kestrel before providing HTTP.sys details.
- In code and configuration examples, consider showing Kestrel (cross-platform) examples first, or in parallel with HTTP.sys, to reinforce Linux parity.
- Where Windows-specific tools (like netsh) are mentioned, briefly note that these are not required for Kestrel or on Linux.
- Add a short summary table or section at the top clarifying which features are cross-platform and which are Windows-only.
- Ensure that all critical scenarios (stateless/stateful, internal/external) have Kestrel-based examples and guidance shown first or equally.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on .NET serialization concepts relevant to Azure Service Fabric Reliable Collections. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned for application upgrades, with no Linux/macOS alternatives or parity (e.g., CLI or Bash examples). The main content does not reference Windows-specific tools or patterns, but the ordering and selection of upgrade tutorials may create friction for non-Windows users.
Recommendations
- Add links or references to cross-platform upgrade methods, such as using Azure CLI or Bash scripts, if available.
- Clarify whether PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternative instructions.
- Consider mentioning Visual Studio Code or other cross-platform IDEs for application upgrades.
- Explicitly state if certain upgrade methods are Windows-only, and provide Linux/macOS alternatives where possible.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows development and tools (Visual Studio, PowerShell) before Linux equivalents (Eclipse, Yeoman), but provides parity in describing both environments. No Windows-only tools or examples are given exclusively, and Linux support is clearly acknowledged.
Recommendations
- Consider listing Linux development options before or alongside Windows options to avoid subtle ordering bias.
- Add explicit links to Linux quickstart guides or examples in the 'Next steps' section, not just Windows/.NET quickstart.
- Ensure that all referenced guides (e.g., quickstart) have Linux equivalents easily discoverable.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure Service Fabric Reliable Collections serialization concepts and .NET code examples. However, in the 'Next steps' section, Windows-centric tools (Visual Studio and PowerShell) are mentioned before any Linux/macOS alternatives, and no Linux-native upgrade tooling is referenced. There are no Linux-specific examples or guidance, which may create minor friction for non-Windows users.
Recommendations
- Add links or references to Linux/macOS-compatible upgrade tools, such as Azure CLI or Service Fabric CLI (sfctl), in the 'Next steps' section.
- Include examples or guidance for performing application upgrades on Linux-based Service Fabric clusters.
- Clarify that the serialization concepts and code samples are applicable across platforms, and note any platform-specific differences if relevant.
Service Fabric
Describe a cluster by using Cluster Resource Manager
...ce-fabric-cluster-resource-manager-cluster-description.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides configuration examples for both Windows (ClusterManifest.xml) and cross-platform/standalone (ClusterConfig.json) deployments. However, Windows-specific configuration (ClusterManifest.xml under <WindowsServer>) is presented first and in greater detail, and PowerShell examples are included for service creation and updates, with no Linux CLI or bash equivalents. The documentation references WindowsServer in the infrastructure example, which may create a perception of Windows preference, though it also covers standalone (non-Windows) deployments.
Recommendations
- Add explicit Linux/macOS CLI examples (e.g., using Azure CLI or bash scripts) for service creation and updates alongside PowerShell.
- Clarify that ClusterConfig.json applies to both Windows and Linux standalone clusters, and provide examples for Linux node configuration if applicable.
- Consider presenting cross-platform configuration examples (ClusterConfig.json) before or alongside Windows-specific (ClusterManifest.xml) examples.
- Mention any Linux-specific considerations or differences in Service Fabric cluster setup, if relevant.
- If PowerShell is shown, also show equivalent Azure CLI or bash commands for parity.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, Windows-specific tools and scenarios (such as IIS lift-and-shift and Mirantis Container Runtime) are mentioned in detail, and Windows container examples and links are often presented before or alongside Linux equivalents. The IIS scenario is Windows-only, but this is appropriate given its nature. Overall, Linux support is present and referenced, but Windows tools and examples are slightly more prominent.
Recommendations
- Ensure Linux container examples and tutorials are given equal prominence and placement as Windows examples.
- Add more Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift, Linux-based guest executables) alongside Windows scenarios.
- Clarify when certain features or tools are Windows-only to avoid confusion for Linux users.
- Consider alternating the order of Windows and Linux links/examples to avoid 'windows_first' bias.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. Windows-specific terminology and tools (such as references to Windows services and EXE/DLL files) are mentioned first or exclusively in several sections, especially in the infrastructure concepts and code package descriptions. The explanation of node startup references Windows services and executables without mentioning Linux equivalents or startup patterns. However, Linux is acknowledged in some places (e.g., Docker containers on Linux, guest executables), and the development cluster is noted as available on Windows, Linux, or Mac.
Recommendations
- Add Linux-specific details alongside Windows descriptions, such as how Service Fabric nodes start on Linux (e.g., systemd services, relevant Linux processes).
- When describing code packages, mention typical Linux executable formats (e.g., ELF binaries) and clarify that EXE/DLL is Windows-specific.
- Where Windows services or tools are referenced, provide Linux equivalents or note differences in cluster/node management.
- Ensure examples and terminology are presented in a platform-neutral way, or explicitly call out platform-specific differences.
- Consider alternating the order of Windows and Linux mentions to avoid 'windows_first' bias.
Service Fabric
Deny assignment policy for Service Fabric managed clusters
...cles/service-fabric/managed-cluster-deny-assignment.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples and links for Azure PowerShell before Azure CLI, and references PowerShell-specific modules for Service Fabric management. While both Azure CLI and PowerShell are mentioned, PowerShell is emphasized in the best practices section and linked first for critical operations. This creates a mild Windows bias, as PowerShell is more commonly used on Windows, and Linux/macOS users may prefer CLI or other tools.
Recommendations
- Provide Azure CLI examples and links alongside PowerShell for all operations, especially in the best practices section.
- Clarify that Azure CLI is fully supported on Linux/macOS and can be used for managing Service Fabric clusters.
- Consider listing Azure CLI before PowerShell in tables and guidance to balance visibility.
- Add explicit Linux/macOS usage notes or examples where relevant.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, and provides parity in describing development environments and cluster deployment options. However, Windows development (Visual Studio, PowerShell) is mentioned before Linux development (Eclipse, Yeoman) in the 'Any OS, any cloud' section, and the quickstart link points to a .NET (likely Windows-centric) guide. No explicit Linux example or quickstart is provided or linked directly from this overview page.
Recommendations
- Provide quickstart links for both Windows (.NET) and Linux (Java/.NET Core) users in the 'Next steps' section.
- Mention Linux development options before or alongside Windows options in relevant sections.
- Ensure that examples and links are balanced between Windows and Linux, or clarify when a guide is Windows-specific.
- Add a brief note in the 'Any OS, any cloud' section highlighting parity and linking to both Windows and Linux getting started guides.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support on both Linux and Windows, but there is a slight bias towards Windows in the ordering and emphasis of examples and scenarios. Windows-specific tools (Mirantis Container Runtime, DockerEE) are mentioned, and IIS lift-and-shift scenarios are highlighted first. However, Linux support is clearly described, and Linux tutorials are linked alongside Windows equivalents.
Recommendations
- Ensure Linux examples and scenarios are presented before or alongside Windows examples, especially in introductory sections.
- Expand Linux-specific scenarios (e.g., NGINX, Apache, Node.js) to match the detail given to Windows/IIS scenarios.
- Mention Linux container runtimes and tools (e.g., containerd, Podman) if relevant, not just Docker.
- Balance the order of quickstart/tutorial links so Linux and Windows are equally prominent.
- Add explicit notes about parity and limitations for each platform where applicable.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in image cleanup, and mentions Windows images before Linux equivalents. No Linux-specific examples or references are provided, and the examples for skipping images focus on Windows images first.
Recommendations
- Add examples and references for common Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
- Clarify that image cleanup applies equally to Linux containers, and provide Linux-focused guidance where relevant.
- Mention Linux container base images in descriptions and examples alongside Windows images to ensure parity.
- If there are platform-specific behaviors (e.g., cleanup differences between Windows and Linux containers), document them explicitly.
Service Fabric
Understanding periodic backup configuration
...-fabric-backuprestoreservice-configure-periodic-backup.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page for configuring periodic backups in Azure Service Fabric shows minor Windows bias. The only on-premises backup storage example is a Windows file share, with authentication options focused on Windows (Integrated Windows Authentication, username/password). No Linux or cross-platform file share options (such as NFS or SMB on Linux) are mentioned, nor are Linux-specific authentication patterns or examples provided. All other examples (Azure Blob storage) are platform-neutral, and no PowerShell or Windows-first patterns are present.
Recommendations
- Add examples for configuring backup storage to Linux-compatible file shares (e.g., NFS, SMB on Linux).
- Mention authentication options for Linux environments, such as Kerberos, or how to access SMB shares from Linux nodes.
- Clarify whether the file share backup storage option is Windows-only or if it can be used from Linux Service Fabric clusters.
- If Linux is not supported for file share backups, explicitly state this limitation.
Service Fabric
Azure Service Fabric security best practices
...rvice-fabric/service-fabric-best-practices-security.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for most security best practices, but Windows examples and tools (such as PowerShell and Windows Defender) are often presented first or exclusively. Windows-specific recommendations (e.g., Windows Defender, security baselines) are included without Linux equivalents, and PowerShell commands are used for Windows encryption, while Linux uses bash/openssl. Some sections, like Windows Defender and security baselines, are Windows-only, but this is appropriate given their nature. However, minor friction exists for Linux users due to Windows-first ordering and lack of Linux parity in some recommendations.
Recommendations
- Where possible, provide Linux-first or parallel examples (e.g., bash/openssl before or alongside PowerShell).
- Explicitly mention Linux alternatives for Windows-specific tools (e.g., recommend ClamAV or other Linux antivirus solutions in the Windows Defender section).
- For security baseline recommendations, link to Linux security best practices (e.g., CIS Linux benchmarks) alongside Windows baselines.
- Ensure that Linux guidance is as prominent and detailed as Windows guidance throughout the document.
Service Fabric
Azure Service Fabric Docker Compose Deployment Preview
...ticles/service-fabric/service-fabric-docker-compose.md
Low 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 commands are presented first and in greater detail, which may suggest a Windows-first bias. The CLI examples are present and usable on Linux/macOS, but PowerShell is emphasized, potentially creating friction for non-Windows users.
Recommendations
- Present CLI (sfctl) examples before PowerShell, or at least equally.
- Explicitly mention that sfctl is cross-platform and preferred for Linux/macOS users.
- Add notes clarifying that PowerShell examples are for Windows users, while sfctl is for Linux/macOS.
- Ensure all critical operations are covered in both PowerShell and CLI sections.
- Consider adding bash/zsh shell example snippets for Linux/macOS users where relevant.
Service Fabric
Reliable services app manifest examples
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/service-fabric/service-fabric-manifest-example-reliable-services-app.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page provides Service Fabric application and service manifest examples, but exhibits mild Windows bias. Windows-specific concepts (such as running scripts via .bat files, referencing PowerShell modules, and using Windows account types like NetworkService and Administrators) are present. The only script example is a Windows batch file (Setup.bat), and the documentation references using the ServiceFabric PowerShell module to create service instances. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or account types mentioned.
Recommendations
- Add examples for running startup scripts using cross-platform formats (e.g., .sh for Linux/macOS).
- Mention Linux account types and how principals/policies map to Linux environments.
- Reference Service Fabric CLI (sfctl) or other cross-platform tools alongside PowerShell.
- Clarify which manifest settings are platform-agnostic and which require Windows-specific configuration.
- Provide guidance or links for Linux/macOS users deploying Service Fabric applications, including any differences in manifest usage or deployment steps.
Service Fabric
Reliable Collection object serialization
...c-reliable-services-reliable-collections-serialization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples and references primarily in C# and .NET, which are cross-platform but historically associated with Windows. In the 'Next steps' section, Windows tools (Visual Studio and PowerShell) are mentioned before any Linux alternatives, and there is no explicit mention of Linux/macOS tooling or workflows. However, the core serialization concepts are platform-agnostic and do not depend on Windows-specific features.
Recommendations
- Add explicit guidance or examples for Linux/macOS users, such as using CLI tools or cross-platform editors (e.g., VS Code, dotnet CLI).
- In the 'Next steps' section, include links or instructions for upgrading applications using Linux/macOS-compatible tools (e.g., Bash scripts, Azure CLI).
- Clarify that Service Fabric Reliable Collections and serialization are supported on both Windows and Linux clusters, and note any platform-specific differences if relevant.
Service Fabric
Learn Azure Service Fabric terminology
...es/service-fabric/service-fabric-technical-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally platform-neutral and describes Service Fabric concepts applicable to both Windows and Linux. However, there are subtle signs of Windows bias: Windows terminology and tools (such as 'Windows service', 'FabricHost.exe', 'EXE/DLL files') are mentioned first or exclusively in some sections, and Windows-specific executables are referenced without always providing Linux equivalents or clarifying cross-platform behavior. Linux is mentioned in some places (e.g., Docker containers), but Windows patterns and terminology are more prominent.
Recommendations
- Where Windows-specific executables or services are mentioned (e.g., 'FabricHost.exe', 'EXE/DLL files'), clarify if/how these concepts map to Linux deployments (e.g., systemd services, ELF binaries).
- When describing node startup and service management, include Linux equivalents or note differences in process management.
- Ensure examples and terminology are balanced: mention Linux alongside Windows when discussing executables, containers, or deployment models.
- Add explicit statements or links about Linux support and any platform-specific differences in Service Fabric operation.
Service Fabric
Azure Service Fabric container image management
.../articles/service-fabric/container-image-management.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation references Windows container base images (microsoft/windowsservercore, microsoft/nanoserver) as default exclusions in image cleanup, but does not mention Linux container base images or provide Linux-specific examples. The configuration examples and descriptions are generic, but the only concrete image examples are Windows-centric. There are no PowerShell or Windows tool references, but the bias is present in the image examples and omission of Linux parity.
Recommendations
- Add examples of Linux container base images (e.g., 'docker.io/library/ubuntu', 'docker.io/library/alpine') in the 'ContainerImagesToSkip' setting.
- Clarify whether the cleanup features and settings apply equally to Linux containers and Windows containers.
- Include a note or section about Linux container image management, especially if there are any differences or considerations.
- Provide sample configurations or scenarios for clusters running Linux containers.
Service Fabric
Overview of Azure Service Fabric
...ain/articles/service-fabric/service-fabric-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows and Linux support for Azure Service Fabric, including development and deployment. However, Windows development (with .NET SDK, Visual Studio, PowerShell) is described first, while Linux development (Java SDK, Eclipse, Yeoman) is mentioned second. There are no explicit Linux/PowerShell-only examples or tools, but the ordering and emphasis slightly favor Windows.
Recommendations
- Present Windows and Linux development options in parallel, rather than listing Windows first.
- Add links to Linux quickstart guides and documentation alongside Windows equivalents.
- Ensure example workflows and tool references are balanced for both platforms.
- Consider including a brief comparison table of Windows and Linux development environments.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits mild Windows bias. The introductory section and terminology focus primarily on 'custom windows images', and the only CLI example provided is in PowerShell. While there are references to Linux custom image creation and Azure CLI for browsing images, the main workflow and examples are Windows-centric, and Linux-specific command-line examples are missing.
Recommendations
- Clarify that both Windows and Linux custom images are supported, and update language to refer to 'custom images' rather than 'custom windows images' where appropriate.
- Provide equivalent Linux command-line examples (e.g., Azure CLI or Bash) for role assignment and other operations, alongside PowerShell.
- Include explicit guidance or links for deploying Linux custom images to Service Fabric Managed Clusters.
- Ensure ARM template examples and explanations are generic and applicable to both Windows and Linux node types.
Service Fabric
Overview of Service Fabric and containers
...s/service-fabric/service-fabric-containers-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides a balanced overview of Service Fabric container support for both Linux and Windows. However, Windows-specific tools (IIS, Mirantis Container Runtime, DockerEE) and scenarios (IIS lift and shift) are mentioned before or more prominently than Linux equivalents. Windows container examples and links are sometimes listed before Linux ones, and Windows-specific terminology is used in some sections. Linux examples and tutorials are present, but Windows scenarios are slightly prioritized.
Recommendations
- Ensure Linux and Windows examples/tutorials are presented in parallel or with Linux examples listed first where appropriate.
- Add Linux-specific scenarios (e.g., Apache/Nginx lift-and-shift, systemd-based applications) to balance the IIS lift-and-shift Windows scenario.
- Mention Linux container runtimes and tools (e.g., containerd, Podman) alongside Docker, where relevant.
- Clarify that Service Fabric supports both Linux and Windows containers equally, and highlight cross-platform parity in capabilities.
- Where Windows-specific tools are discussed, provide Linux equivalents or note their absence if not applicable.