App Service
432
Total Pages
240
Linux-Friendly Pages
192
Pages with Bias
44.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2121 issues found
Showing 1251-1275 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-custom-container.md
...main/articles/app-service/tutorial-custom-container.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias in several ways. The Windows section appears first and is more detailed in certain areas, with exclusive use of Windows tools (Visual Studio, Windows Explorer, PowerShell scripts) and workflows. The Windows example is tightly coupled to Visual Studio and Windows-specific features (such as installing fonts via Windows Explorer and using PowerShell scripts in Dockerfiles), with no equivalent Linux example for similar scenarios (e.g., custom OS integration, font installation). The Linux section, while comprehensive for a generic Python/Flask app, does not mirror the Windows scenario or provide parity for .NET or custom OS integration use cases.
Recommendations
- Provide Linux-first or at least parallel Linux and Windows sections, ensuring neither is prioritized in order or detail.
- For every Windows-specific tool or workflow (e.g., Visual Studio, Windows Explorer, PowerShell), provide equivalent Linux instructions (e.g., VS Code, terminal commands, Bash scripts).
- Include a Linux example that demonstrates how to migrate a .NET app with custom OS dependencies (such as custom fonts or libraries) to a Linux container, mirroring the Windows scenario.
- Avoid assuming the user is on Windows by default; ensure all prerequisites and setup steps have Linux equivalents.
- Where PowerShell scripts are used in Dockerfiles for Windows, provide Bash script equivalents for Linux.
- Ensure that screenshots and step-by-step instructions are available for both platforms, not just Windows.
- Explicitly mention any platform-specific limitations or differences, and guide users on how to address them on Linux.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-sql-database.md
...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows-centric bias by prioritizing Windows/Visual Studio workflows, using PowerShell and Windows-specific tools for critical steps (such as granting SQL permissions), and omitting explicit Linux/macOS command-line or tooling alternatives for key operations. Linux and cross-platform development environments are only briefly referenced, and there are no concrete examples or guidance for performing database permission steps from non-Windows systems.
Recommendations
- Provide explicit Linux/macOS alternatives for all steps, especially for granting SQL permissions (e.g., using sqlcmd on Linux, Azure Data Studio, or cross-platform tools).
- Include examples using bash and cross-platform shells for all CLI operations, not just Azure CLI.
- Add a section or tab for Linux/macOS development environments, detailing how to configure and debug apps using VS Code or JetBrains Rider on those platforms.
- When mentioning Visual Studio, clarify that Visual Studio Code is cross-platform and provide parity in instructions.
- Avoid assuming PowerShell or Windows-only tools are available; always offer a cross-platform equivalent.
- For SQL permission steps, show how to use sqlcmd or Azure Data Studio on Linux/macOS, or provide T-SQL scripts that can be run from any platform.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-dotnet-deploy-vs.md
.../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments, specifically Visual Studio on Windows. All examples and instructions assume the use of Visual Studio, with no mention of Linux or cross-platform alternatives. There are no command-line or non-Windows deployment examples, and all tooling references (e.g., Solution Explorer, dialog boxes, right-click menus) are specific to Windows/Visual Studio. Linux users or those using other IDEs are not provided with equivalent guidance.
Recommendations
- Add instructions for developing and deploying WebJobs using cross-platform tools such as the Azure CLI, .NET CLI, or Visual Studio Code.
- Include Linux-specific examples for creating, configuring, and deploying WebJobs.
- Mention and document alternative workflows for non-Windows environments, such as using GitHub Actions, Azure DevOps, or command-line deployment.
- Clarify which steps are Windows/Visual Studio-specific and provide parity guidance for macOS and Linux users.
- Reference and link to documentation on deploying WebJobs without Visual Studio, including from Linux/macOS terminals.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-sdk-get-started.md
...b/main/articles/app-service/webjobs-sdk-get-started.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows and Visual Studio users. All command-line examples use PowerShell syntax and the Visual Studio Package Manager Console, which are Windows-specific. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, .NET CLI, or terminal-based workflows). Visual Studio is assumed as the only development environment, and Windows UI navigation is described throughout. No mention is made of Linux equivalents or how to perform these steps on non-Windows systems.
Recommendations
- Provide .NET CLI equivalents for all NuGet package installation commands (e.g., 'dotnet add package ...'), and show these alongside or before PowerShell examples.
- Include instructions for creating and running the project using cross-platform tools such as VS Code or JetBrains Rider, not just Visual Studio.
- Add guidance for Linux and macOS users, including how to configure and run the app from the terminal.
- Replace or supplement Visual Studio UI navigation steps with command-line alternatives where possible.
- Explicitly state that the tutorial can be followed on Windows, Linux, or macOS, and clarify any platform-specific requirements.
- Show how to set environment variables and configuration files on Linux/macOS (e.g., using export or editing files in the terminal).
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is primarily focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (such as Test-NetConnection and netstat -aon) are given using Windows/PowerShell tools, with no Linux/macOS equivalents provided. The use of Windows-specific commands and lack of Linux guidance creates friction for users who may need to debug from non-Windows environments, even if the feature itself is Windows-only.
Recommendations
- Clarify early and prominently that all operational steps and troubleshooting are Windows-specific due to the feature limitation.
- Where troubleshooting involves connecting to VMs or network endpoints, provide equivalent Linux/macOS commands (e.g., 'nc', 'telnet', 'ss', 'netstat', 'dig') alongside PowerShell examples.
- Explicitly state that Linux App Service plans cannot use this feature, and link to Linux-compatible alternatives (such as regional virtual network integration).
- Add a section summarizing Linux/macOS limitations and recommended approaches for similar tasks.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for RBAC permissions, but PowerShell is given equal prominence and referenced in multiple places. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned as options for exporting certificates, while Linux tools (OpenSSL) are referenced but not explained in as much detail. Windows tooling is mentioned before Linux equivalents in some sections, and links to Windows documentation are provided for certificate export. The FAQ and automation sections reference PowerShell scripts alongside CLI, but do not provide Bash or Linux-native scripting examples.
Recommendations
- Provide Linux/macOS-specific instructions and examples for certificate export, including detailed OpenSSL usage and troubleshooting.
- Add Bash scripting examples for automation alongside PowerShell and Azure CLI.
- When referencing certificate export tools, mention OpenSSL first, and provide links to Linux/macOS documentation.
- Ensure parity in screenshots and UI descriptions for Linux/macOS users where relevant.
- Clarify which steps are OS-agnostic and which are Windows-specific, to help users on non-Windows platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is structured with clear pivots for Windows and Linux containers, providing parity in most sections. However, Windows-specific examples, tools (PowerShell), and terminology (e.g., C:\home) are often presented first or in more detail. PowerShell commands are shown alongside Bash/Azure CLI, but Windows-centric explanations (such as IIS, .NET Framework, and Windows Server images) are more prominent. Some sections (like customizing memory and CPU cores) provide Windows-specific instructions and verification steps using PowerShell, with no Linux equivalent. The use of Windows terminology (e.g., C:\home) sometimes appears in Linux sections, which could confuse Linux users.
Recommendations
- Ensure Linux examples and terminology (e.g., /home instead of C:\home) are presented first or equally alongside Windows examples in all relevant sections.
- Provide Linux-specific verification steps (e.g., checking CPU cores or memory limits) using Bash or Linux tools, not just PowerShell.
- Clarify when instructions or settings differ between Windows and Linux containers, and avoid mixing Windows paths or concepts in Linux container guidance.
- Where PowerShell is used, ensure Bash/Linux equivalents are always present and equally detailed.
- Review sections for unnecessary Windows-centric language or assumptions, especially in Linux pivots.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific certificate store access is described in detail with C# and Java code samples, while Linux guidance is less prominent and mostly limited to file-based access. Windows examples and terminology (certificate store, thumbprint, environment variables) are presented first and in greater depth. For non-Windows languages (Node.js, PHP, Python), Linux-specific code samples are missing, and users are referred to external documentation. Windows tools and patterns (certificate store, environment variables) are emphasized, and Linux equivalents are not always provided.
Recommendations
- Add Linux-specific code samples for popular languages (Node.js, Python, PHP, Java) showing how to load certificates from the injected file paths.
- Present Linux and Windows guidance in parallel, rather than Windows-first, especially in introductory and critical sections.
- Expand explanations of Linux certificate handling, including environment variables and file permissions.
- Clarify any differences in certificate formats or handling between Windows and Linux containers.
- Provide links to relevant Linux documentation or official guides for certificate handling in various languages.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias: Windows examples and certificate store access patterns are presented first and in greater detail, with C# and Java code samples for Windows, while Linux examples are less prominent and mostly limited to file-based access. There are no direct code examples for Linux in languages other than C#, and users of Node.js, PHP, Python, or Java on Linux are referred to external documentation. Windows-specific tools and patterns (certificate store, thumbprint usage) are emphasized throughout.
Recommendations
- Add code examples for Linux environments in popular languages such as Node.js, Python, Java, and PHP, showing how to load certificates from the provided file paths.
- Present Linux and Windows examples in parallel or with equal prominence, especially in sections describing certificate access.
- Clarify at the beginning that both Windows and Linux are supported, and provide a summary table of differences.
- Reduce reliance on Windows-specific terminology and tools (e.g., certificate store, thumbprints) when describing cross-platform approaches.
- Link to or provide sample scripts for common Linux certificate management tasks.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.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 RBAC assignments, but PowerShell is given equal prominence and referenced in multiple places. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux alternatives (OpenSSL) are referenced but not explained in detail. Windows tooling is presented first or equally, and some export instructions link to Windows-specific guides. Linux/macOS users may need to infer steps or consult external documentation for parity.
Recommendations
- Provide explicit Linux/macOS instructions for certificate export (e.g., OpenSSL usage, file paths, and troubleshooting).
- Include more detailed OpenSSL command examples, especially for common scenarios and error handling.
- Add links to Linux/macOS certificate management guides, or summarize key steps inline.
- When mentioning Windows tools (IIS, Certreq.exe), also mention Linux/macOS equivalents or clarify when Windows-only steps are required.
- Ensure Azure CLI examples are shown before or alongside PowerShell, and clarify cross-platform support.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific instructions and code samples (especially for C# and Java) are presented first and in greater detail, with Linux examples either missing, less detailed, or deferred to external language documentation. Windows certificate store access is explained thoroughly, while Linux approaches are less emphasized. Some sections provide only Windows code, or refer Linux users to 'see the documentation for the respective language.'
Recommendations
- Provide parallel Linux code examples (e.g., for Java, Node.js, Python, PHP) for loading certificates, not just C#.
- Present Linux and Windows instructions/examples side-by-side or in tabs throughout, not just in container sections.
- Expand on Linux-specific certificate handling (e.g., permissions, file formats, environment variables) where relevant.
- Avoid referring Linux users to external documentation for basic tasks that are explained in detail for Windows.
- Where possible, use cross-platform code samples (e.g., .NET Core) and clarify any OS-specific differences.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is focused on gateway-required virtual network integration, which is explicitly stated to be a Windows-only feature. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command) are given only for Windows, with no Linux/macOS equivalents. Windows tools and patterns (PowerShell, netstat -aon) are mentioned exclusively or before any cross-platform alternatives. Linux users are told the feature is unsupported, but troubleshooting guidance is Windows-centric, creating friction for users managing hybrid environments.
Recommendations
- Clarify early and prominently that gateway-required virtual network integration is Windows-only, and that Linux apps are not supported.
- Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (e.g., nc, netcat, lsof, ss, curl) for users managing hybrid environments or diagnosing issues from non-Windows hosts.
- Add links or references to regional virtual network integration documentation for Linux users, as recommended throughout the page.
- Explicitly state that all examples and tools are Windows-specific due to feature limitations, to avoid confusion.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section requires installation of Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS alternatives. This creates friction for non-Windows users who wish to use Hybrid Connections for outbound access from Azure App Service.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative outbound connectivity options for Linux/macOS users.
- Add examples or guidance for Linux App Service users, especially in sections where Windows-specific tools are referenced.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows examples (C#, Java) are presented first and in detail, with explicit code for accessing certificates from the Windows certificate store. Linux guidance is less prominent and often deferred to external documentation, especially for non-.NET languages. Windows-specific tools and patterns (certificate store, environment variables, .NET Framework) are described in depth, while Linux and cross-platform approaches are less thoroughly covered.
Recommendations
- Provide Linux and cross-platform code examples (e.g., Python, Node.js, Java, PHP) for loading certificates, not just C#.
- Present Linux and Windows examples side-by-side or in parallel tabs, rather than Windows-first.
- Expand the 'Load a certificate from a file' section with concrete Linux and containerized app examples, including code for common languages.
- Clarify when guidance is Windows-specific and offer equivalent Linux instructions where possible.
- Reference Linux tools and patterns (e.g., OpenSSL, Linux environment variables) alongside Windows tools.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is evidence of Windows bias: Windows-specific paths (e.g., D:\home) and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS) are mentioned frequently and often before Linux equivalents. Windows terminology and examples (such as referencing Windows time zones, IIS, and .bat files) appear throughout, sometimes without Linux alternatives or with Linux details added as secondary notes. Build automation and logging sections are Windows-centric, with Linux (Oryx) build configuration presented as a separate tab, but less detailed. Some environment variables and explanations are Windows-only, with Linux coverage sometimes limited or appended.
Recommendations
- Ensure Linux examples and paths (e.g., /home) are given equal prominence alongside Windows ones, especially in introductory tables and explanations.
- Where Windows tools (e.g., msbuild, Web Deploy) are referenced, provide Linux equivalents or clarify when features are Windows-only.
- Expand Linux-specific build automation and logging documentation to match the detail provided for Windows/Kudu.
- Avoid presenting Windows terminology (paths, tools, config files) first unless the feature is Windows-only; use neutral or dual-platform language.
- Add explicit Linux/macOS guidance for configuring environment variables and app settings where currently only Windows instructions are given.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths, tools, and terminology (such as IIS, msbuild, Web Deploy/MSDeploy, and Windows directory structures like D:\home) are referenced first or exclusively in several sections. Windows examples and settings often precede Linux equivalents, and some explanations default to Windows-centric language. Linux-specific details are present but sometimes secondary or less detailed.
Recommendations
- Ensure Linux paths and examples are provided alongside Windows ones, especially in introductory tables and explanations.
- When referencing tools (e.g., msbuild, Web Deploy), clarify Linux equivalents or alternatives (such as Oryx for build automation).
- Balance the order of presentation so Linux and Windows settings/examples are given equal prominence.
- Expand Linux-specific explanations where they are brief or missing, especially for deployment, logging, and build automation.
- Where possible, use platform-neutral language or clarify when a setting is platform-specific.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific certificate store access is described in detail with C# and Java code samples, and the Windows workflow is presented first and most thoroughly. Linux examples are limited, only shown for C# in containers, and users of other languages (Node.js, PHP, Python, Java) are told to consult external documentation. Windows tools and patterns (certificate store, thumbprints, environment variables) are emphasized, and Linux equivalents are not given equal prominence or coverage.
Recommendations
- Add explicit Linux (and macOS, if relevant) code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the file paths provided by App Service.
- Present Linux and Windows workflows in parallel or in clearly separated tabs, rather than focusing on Windows first.
- Include more discussion of Linux-specific certificate handling patterns, such as using OpenSSL or language-specific libraries to load .p12/.der files.
- Clarify any differences in certificate formats or handling between Windows and Linux environments.
- Where possible, provide direct code examples for Linux containers and apps, not just references to external documentation.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation generally provides platform-agnostic guidance for managing TLS/SSL certificates in Azure App Service, but there are subtle Windows biases. When discussing exporting certificates, Windows tools (IIS, Certreq.exe) are mentioned explicitly, while Linux/macOS equivalents are not. PowerShell is given as an example for RBAC assignment, and the FAQ links to both Azure CLI and PowerShell, but the PowerShell script is listed second. There are no explicit Linux/macOS-specific instructions for certificate export or management, and no mention of common Linux certificate tools beyond OpenSSL.
Recommendations
- When referencing certificate export, provide explicit Linux/macOS guidance (e.g., using OpenSSL for all platforms, or mentioning 'certutil' for Linux).
- When mentioning Windows tools like IIS or Certreq.exe, also mention Linux/macOS equivalents or clarify that OpenSSL is cross-platform.
- For scripting examples (e.g., RBAC assignment), ensure both Azure CLI and PowerShell are presented in parallel, and clarify which is cross-platform.
- Add a short section or note clarifying that all certificate management steps (except those explicitly using Windows tools) can be performed on Linux/macOS using OpenSSL.
- In the FAQ and automation sections, ensure parity by listing Azure CLI and PowerShell examples together, and consider adding Bash or cross-platform scripting examples.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section requires installation of Hybrid Connection Manager on Windows Server, with no mention of Linux/macOS alternatives. This creates friction for non-Windows users, as Linux-based relay agents or instructions are not provided. Other networking features are described in a cross-platform way, and no PowerShell or Windows-first examples are present.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide download links or instructions if so.
- If Linux/macOS support is unavailable, explicitly state this limitation and suggest alternative approaches for Linux users.
- Where possible, provide examples or guidance for configuring networking features from Linux/macOS environments (e.g., using Azure CLI, Bash, etc.).
- Review other sections for implicit Windows tool references and ensure parity in documentation for Linux/macOS users.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The primary, detailed code examples for loading certificates are given for Windows (C# and Java using the Windows certificate store), with Linux-specific guidance and examples appearing later and being less comprehensive. Non-Windows languages (Node.js, PHP, Python, Java) are referenced only by suggesting users consult external documentation, with no direct examples provided. Windows-specific tools and patterns (certificate store, environment variables, and app settings) are explained in detail, while Linux equivalents are less emphasized or lack parity in example depth.
Recommendations
- Provide direct, in-page code examples for loading certificates in popular languages (Node.js, Python, Java, PHP) for both Windows and Linux environments.
- Ensure Linux examples are as detailed as Windows ones, including file paths, environment variables, and error handling.
- Present Windows and Linux guidance in parallel or with equal prominence, rather than leading with Windows.
- Clarify any platform-specific limitations or differences up front, and link to language- or OS-specific best practices where appropriate.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is generally cross-platform and does not focus on Windows-specific features. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux/macOS support or alternatives. This creates friction for Linux users who may wish to use Hybrid Connections but are not provided guidance or examples.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide installation instructions or alternatives if so.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux users.
- Review other sections for tool-specific instructions and ensure parity for Linux/macOS where possible.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page provides examples and instructions for both Windows and Linux users in most sections, but there are notable Windows biases. Windows directory paths (%HOME%, D:\home\site\wwwroot) and tools (Kudu DebugConsole, FTP) are mentioned first or exclusively in several places. PowerShell is referenced alongside Azure CLI for scripting, but Linux shell examples are not provided. The instructions for creating the _backup.filter file use Windows-style paths and refer to Windows-specific folders. However, Linux parity is generally maintained for core backup/restore tasks, and Azure CLI is cross-platform.
Recommendations
- Provide Linux/macOS equivalents for directory paths (e.g., /home/site/wwwroot instead of D:\home\site\wwwroot).
- Include Linux shell scripting examples alongside PowerShell in the 'Automate with scripts' section.
- Clarify that tools like Kudu DebugConsole and FTP are available for both Windows and Linux App Service apps, and provide Linux-specific instructions where relevant.
- Show Linux directory structure and path examples in the partial backup section.
- Ensure that references to environment variables (e.g., %HOME%) include Linux equivalents ($HOME).
App Service
Tutorial for event-driven background processing with the WebJobs SDK
...b/main/articles/app-service/webjobs-sdk-get-started.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio 2022. All instructions, screenshots, and examples reference Windows tools and workflows (e.g., Visual Studio menus, Package Manager Console, PowerShell commands). There are no examples or guidance for Linux/macOS users, such as using .NET CLI, VS Code, or alternative package management methods. This creates friction for non-Windows users, though the underlying .NET 8/WebJobs SDK is cross-platform.
Recommendations
- Add instructions for creating and managing the project using .NET CLI (dotnet new, dotnet add package, etc.), which works on Linux/macOS.
- Include examples for installing NuGet packages via CLI, not just via Visual Studio Package Manager Console.
- Provide guidance for running and debugging the project using VS Code or other cross-platform editors.
- Mention any platform-specific limitations (if any) and clarify that WebJobs SDK projects can be developed and run on Linux/macOS.
- Add screenshots or descriptions for Azure Portal steps that are not OS-specific.
- Explicitly note that Visual Studio is optional and provide parity steps for Linux/macOS users.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page provides a comprehensive reference for environment variables and app settings in Azure App Service, covering both Windows and Linux scenarios. However, there is a notable Windows bias: Windows-specific tools (such as Kudu, Web Deploy/MSDeploy, IIS, and Windows paths) are mentioned first or exclusively in several sections, and Windows-centric terminology and examples (e.g., `%HOME%`, `D:\home`, `.dll` extensions, Windows-specific build automation) appear before or more frequently than Linux equivalents. Linux-specific details are often present but secondary, and some settings are described primarily in Windows terms with Linux notes added later. The build automation section is split into Windows (Kudu) and Linux (Oryx) tabs, but the Windows tab is presented first. Some environment variables and features are described only for Windows, with Linux coverage less prominent.
Recommendations
- Ensure Linux examples and terminology are presented alongside Windows examples, not after or as an afterthought.
- When describing environment variables, provide both Windows and Linux path examples (e.g., `D:\home` and `/home`).
- In build automation sections, consider presenting Linux (Oryx) and Windows (Kudu) equally, or default to the user's platform if possible.
- Where Windows tools (e.g., Web Deploy/MSDeploy, IIS, .dll) are mentioned, clarify Linux alternatives or note if not applicable.
- Review language-specific settings to ensure Linux-specific variables and behaviors are described with equal detail and clarity.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific approaches and code samples (especially for certificate store access) are presented first and in greater detail, with C# and Java examples for Windows but only C# examples for Linux. Instructions for non-Windows platforms and languages (Node.js, PHP, Python, Java) are deferred to external documentation. Windows tools and patterns (certificate store, environment variables, user profile loading) are described in detail, while Linux equivalents are less thoroughly covered.
Recommendations
- Provide equivalent code samples for Linux for all languages shown for Windows (e.g., Java, not just C#).
- Include explicit Linux examples earlier in the document, not only in container-specific sections.
- Offer direct code snippets or guidance for popular non-Windows languages (Node.js, Python, PHP) on both Windows and Linux, rather than referring users to external documentation.
- Balance the order of presentation so Linux and Windows approaches are shown side-by-side or in parallel sections/tabs.
- Clarify when a feature or approach is Windows-only, and provide clear Linux alternatives where possible.