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 1376-1400 of 2121 flagged pages
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 generally provides cross-platform guidance, but there are some areas where Windows tools and patterns are mentioned first or exclusively. For example, when exporting certificates, Windows tools like IIS and Certreq.exe are referenced, and PowerShell is given as a primary automation example alongside Azure CLI. In automation and certificate export sections, Linux/macOS equivalents are not always provided or are mentioned after Windows tools.
Recommendations
- When referencing certificate export, provide explicit Linux/macOS alternatives (e.g., OpenSSL commands) alongside or before Windows tools like IIS/Certreq.exe.
- In automation sections, ensure that Azure CLI examples are shown before or alongside PowerShell, and clarify that both are cross-platform.
- Where possible, add bash/shell script examples for common tasks (such as certificate management) to improve parity for Linux/macOS users.
- Review screenshots and UI instructions to ensure they are not overly Windows-centric if the portal experience is the same across platforms.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents Azure App Service plans in a cross-platform manner, mentioning both Windows and Linux as supported operating systems. However, there is a notable Windows bias in the 'Managed Instance on Azure App Service (preview)' section, which is exclusively Windows-focused and highlights Windows-specific features and tools (e.g., PowerShell, RDP, IIS customization). Additionally, some links and feature tables reference Windows pricing details first, and there are no Linux-specific examples or guidance for Linux users in areas where parity might be relevant.
Recommendations
- Add explicit Linux examples or guidance where applicable, such as deployment, scaling, and feature availability.
- Clarify which features and tiers are available for Linux-based App Service plans, especially in feature tables and pricing links.
- When introducing new features (like Managed Instance), clearly state their OS limitations upfront and provide equivalent Linux guidance or alternatives if available.
- Ensure that documentation links (e.g., pricing details) do not default to Windows unless the feature is Windows-only.
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
Missing Linux Example
Summary
The documentation page provides comprehensive coverage of environment variables and app settings for Azure App Service, but there is a noticeable Windows bias. Windows-specific paths (e.g., D:\home), tools (e.g., msbuild, Web Deploy/MSDeploy), and configuration patterns are often mentioned first or exclusively, with Linux equivalents sometimes missing or described later. Several examples and explanations use Windows-centric terminology, and some environment variables reference Windows-only features or behaviors, even when Linux equivalents exist. In some sections, Linux-specific details are present but less emphasized or lack parity in examples.
Recommendations
- Ensure Linux and macOS paths (e.g., /home) are shown alongside Windows paths in all examples and tables.
- When describing environment variables, provide both Windows and Linux usage patterns and default values, especially for file paths and deployment behaviors.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which platform is mentioned first, or use neutral language).
- Where Windows tools (e.g., msbuild, Web Deploy/MSDeploy) are referenced, include Linux alternatives (e.g., Oryx, zip deploy) and provide links to relevant documentation.
- Add explicit Linux/macOS examples for environment variable usage, especially in sections where only Windows examples are given.
- Clearly mark Windows-only settings and features to avoid confusion for Linux 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 provides detailed, step-by-step code examples for accessing certificates in Windows apps (including C# and Java using the Windows certificate store), but offers only brief or generic guidance for Linux apps and containers. Linux-specific code samples are limited to C#, with other languages (Node.js, PHP, Python, Java) being referenced only as 'see the documentation for the respective language.' Windows patterns and tools (certificate store, thumbprint usage, environment variables) are explained in detail and appear first in most sections, while Linux equivalents are less emphasized or missing.
Recommendations
- Add concrete code examples for loading certificates in Linux containers for popular languages such as Node.js, Python, Java, and PHP.
- Provide more detailed explanation of Linux certificate handling patterns, including how to use environment variables and file paths in various languages.
- Ensure Linux and Windows guidance are presented in parallel, with equal detail and visibility.
- Include links to relevant Linux language documentation or official guides for certificate handling.
- Consider adding a comparison table or section summarizing differences and similarities between Windows and Linux certificate access in App Service.
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
Missing Linux Example
Summary
The documentation page provides environment variable references for Azure App Service, covering both Windows and Linux scenarios. However, there is a noticeable bias toward Windows: Windows paths and conventions are often mentioned first, Windows-specific tools (such as msbuild, Web Deploy/MSDeploy, IIS, and .NET Framework) are referenced without equal Linux alternatives, and examples frequently use Windows-style paths (e.g., D:\home) or reference Windows-only features. In several cases, Linux equivalents are mentioned later or not at all, and some sections (such as build automation) provide more detail for Windows (Kudu) than Linux (Oryx).
Recommendations
- Ensure Linux paths and conventions are presented alongside Windows examples, ideally with equal prominence.
- Where Windows tools (e.g., msbuild, Web Deploy) are referenced, provide Linux alternatives or clarify when features are Windows-only.
- Add Linux/macOS-specific examples and usage notes where currently only Windows examples are given.
- In tables and lists, alternate the order of Windows and Linux references, or group them by platform for clarity.
- Expand documentation for Linux build automation (Oryx) to match the detail provided for Windows (Kudu).
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 Azure PowerShell examples for assigning Key Vault permissions, but PowerShell is given equal or slightly more prominence in some sections. In the certificate export section, Windows-specific tools (IIS, Certreq.exe) are mentioned for exporting certificates, with only a brief reference to OpenSSL for Linux/macOS. The FAQ and automation sections link to both CLI and PowerShell scripts, but PowerShell is often mentioned first. There are no Linux/macOS-specific screenshots or portal instructions, and the overall flow assumes familiarity with Windows-centric tools and patterns.
Recommendations
- Ensure that for every PowerShell example, an Azure CLI (cross-platform) equivalent is provided and shown first, or at least in parallel.
- In sections about exporting certificates, provide explicit OpenSSL commands and workflows for Linux/macOS, not just a passing mention.
- Where Windows tools like IIS or Certreq.exe are referenced, add clear alternatives for Linux/macOS users (e.g., OpenSSL commands for generating and exporting certificates).
- Include notes or screenshots that clarify any UI differences for Linux/macOS users, if applicable.
- In automation and FAQ sections, list Azure CLI (cross-platform) scripts before PowerShell scripts to reduce perceived Windows-first bias.
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 provides detailed, step-by-step code examples for accessing certificates in Windows environments (including Windows apps and containers), with C# and Java code focused on the Windows certificate store. Linux guidance is limited to C# file-based loading, with no equivalent code samples for other languages (Node.js, PHP, Python, Java) on Linux. Windows-specific tools and patterns (certificate store, thumbprint usage, environment variables) are described in detail before Linux equivalents, and Windows examples are generally presented first or exclusively.
Recommendations
- Provide equivalent, detailed code examples for Linux environments, especially for popular languages such as Node.js, Python, Java, and PHP.
- Present Linux and Windows guidance in parallel, or use tabs to avoid Windows-first ordering.
- Add explicit instructions or code samples for accessing certificates in Linux containers for languages other than C#.
- Clarify when Windows-specific features (like the certificate store) are not available or relevant on Linux, and offer Linux-native alternatives.
- Reference Linux tools and patterns (such as OpenSSL, PEM/PFX file handling) where appropriate.
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 generally covers both Windows and Linux, but there is a recurring pattern of Windows-centric terminology, examples, and environment variable values being shown first or exclusively. Several variables and descriptions reference Windows paths (e.g., D:\home), Windows-specific tools (e.g., msbuild, Web Deploy/MSDeploy), and Windows configuration files (e.g., applicationHost.config, Web.config) without always providing Linux equivalents or parity in explanation. Some sections (such as Build Automation) give more detail for Windows (Kudu) than Linux (Oryx), and Windows tools are often mentioned before Linux alternatives.
Recommendations
- For every environment variable or feature that behaves differently on Windows and Linux, provide both examples and clarify the differences explicitly.
- When referencing paths, always show both Windows and Linux equivalents (e.g., D:\home and /home).
- When mentioning Windows-specific tools (e.g., msbuild, Web Deploy), also mention Linux equivalents or note when no equivalent exists.
- In tables and lists, alternate or parallelize the order of Windows and Linux information, rather than consistently listing Windows first.
- Expand the Oryx (Linux) build automation section to match the detail level of the Kudu (Windows) section.
- Where features are Windows-only, clearly label them as such to avoid confusion.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC assignment, but PowerShell is given equal prominence, and references to Windows tools (IIS, Certreq.exe) are present for certificate export. The instructions for exporting certificates mention Windows-specific tooling before Linux equivalents (OpenSSL), and the FAQ automation section lists PowerShell and CLI scripts, with PowerShell mentioned second. There are no Linux/macOS-specific examples or explicit parity notes.
Recommendations
- Ensure all automation and scripting examples include both Azure CLI and PowerShell, with CLI (cross-platform) shown first.
- When discussing certificate export, mention OpenSSL (Linux/macOS) before Windows tools (IIS, Certreq.exe), and provide explicit instructions for both platforms.
- Add notes or links for Linux/macOS users where Windows tools are referenced, clarifying alternatives.
- Where screenshots or UI steps are shown, clarify that the Azure portal is platform-agnostic.
- Consider including a short section or callout for Linux/macOS users on common certificate management workflows.
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 presents Windows-centric instructions and examples first, especially for loading certificates in app code. Windows certificate store access is explained in detail for C# and Java, while Linux guidance is limited to file-based access and only C# examples are provided for Linux. There are no Linux-specific code samples for popular languages like Python, Node.js, or Java, and references to those platforms are deferred to external documentation. Windows tools and patterns (certificate store, environment variables, etc.) are described more thoroughly than their Linux equivalents.
Recommendations
- Add Linux-specific code examples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the provided Linux file paths.
- Present Linux and Windows instructions in parallel or in tabs, rather than leading with Windows-only approaches.
- Expand discussion of Linux environment variables and best practices for certificate access, matching the detail given to Windows.
- Clarify which approaches are cross-platform and which are Windows-specific earlier in the document.
- Provide direct links or inline examples for Linux container scenarios in languages other than C#.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation is generally cross-platform, describing both Windows and Linux as supported operating systems for App Service plans. However, the 'Managed Instance on Azure App Service' section is Windows-only and highlights Windows-specific tools (PowerShell, RDP, IIS, registry access, MSI installers, COM components) without mentioning Linux equivalents or alternatives. Windows features and tooling are described in detail, while Linux-specific capabilities or migration scenarios are not discussed, creating a subtle Windows-first bias in advanced hosting scenarios.
Recommendations
- Add a parallel section describing advanced Linux hosting options, if available, or clarify the absence of equivalent features for Linux.
- Where Windows-specific tools (PowerShell, RDP, IIS) are mentioned, note that these are not available on Linux and suggest Linux-native alternatives or workflows where possible.
- Explicitly state the limitations and feature parity between Windows and Linux App Service plans, especially for advanced scenarios.
- Provide links to Linux migration guidance or documentation for legacy Linux workloads.
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
Missing Linux Example
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 are several instances where Windows-specific details, tools, and patterns are mentioned first or exclusively, and Linux equivalents are either referenced later, less prominently, or omitted. Examples and paths often default to Windows formats (e.g., D:\home), and some deployment/build automation sections provide more detail for Windows (Kudu) than Linux (Oryx). Windows tools (such as msbuild, Web Deploy/MSDeploy, IIS, and .bat files) are referenced directly, while Linux alternatives are less emphasized. Some environment variables are described only in Windows contexts, with Linux applicability noted as an aside or not at all.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows examples, especially for environment variable paths and configuration patterns.
- When describing environment variables, list both Windows and Linux default values and usage patterns equally.
- In build automation and deployment sections, expand Linux (Oryx) documentation to match the detail given for Windows (Kudu), including explicit examples and links.
- Avoid listing Windows tools and patterns first unless they are the only supported option; otherwise, alternate or parallelize the order.
- Where environment variables are Windows-only, clearly mark them as such and provide Linux alternatives or note their absence.
- Add more explicit Linux/macOS troubleshooting notes and references where applicable.
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 provides detailed, step-by-step code examples for accessing TLS/SSL certificates in Windows environments (including Windows apps and containers), using Windows certificate store APIs and Java's Windows-MY keystore. In contrast, Linux guidance is limited: Linux-specific code samples are only provided for C#, and other languages (Node.js, PHP, Python, Java) are referenced generically with no examples. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are described first and in more detail, while Linux equivalents are mentioned later and with less depth.
Recommendations
- Add explicit code examples for loading certificates in Linux environments for popular languages (Node.js, Python, Java, PHP), not just C#.
- Present Linux and Windows guidance in parallel, or use tabs to avoid Windows-first ordering bias.
- Expand Linux-specific instructions, including how to handle certificate permissions, file formats, and environment variables.
- Reference Linux tools (such as OpenSSL, keytool, etc.) where appropriate, alongside Windows tools.
- Clarify any differences in certificate handling between Windows and Linux, especially for container scenarios.
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
Missing Linux Example
Summary
The documentation page provides comprehensive coverage of environment variables and app settings for Azure App Service, but there is a noticeable Windows bias. Many examples and descriptions reference Windows paths (e.g., D:\home), Windows-specific tools (e.g., msbuild, Web Deploy/MSDeploy), and Windows conventions before Linux equivalents. Several environment variables and settings are described primarily in the context of Windows, with Linux details often appearing as secondary notes or omitted. Some sections (e.g., build automation, logging, TLS/SSL paths) focus on Windows tools and patterns, with Linux alternatives given less prominence or missing entirely.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows examples, especially for environment variable paths, deployment, and logging.
- Present Linux and Windows instructions in parallel, or use tabs to separate platform-specific guidance, rather than listing Windows first.
- Where Windows tools (e.g., msbuild, Web Deploy/MSDeploy) are mentioned, include Linux-native alternatives (e.g., Oryx, zip deploy, relevant CLI commands) and clarify platform applicability.
- Expand documentation of Linux-specific environment variables and behaviors, especially for logging, TLS/SSL, and build automation.
- Review all examples and default values to ensure Linux paths (e.g., /home/site/wwwroot) are shown as often as Windows paths (e.g., D:\home\site\wwwroot).
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 provides detailed, step-by-step examples for accessing TLS/SSL certificates in Windows apps, including C# and Java code for the Windows certificate store. Linux guidance is present but less detailed, with only C# file-based examples and references to external documentation for other languages. Windows-specific tools and patterns (certificate store, environment variables, app settings) are described first and in more depth, while Linux equivalents are mentioned later and with less coverage.
Recommendations
- Add concrete code examples for loading certificates in popular Linux languages (Node.js, Python, Java, PHP) directly in the documentation, not just references to external docs.
- Provide more detailed explanation of Linux certificate file formats and access patterns, including security best practices.
- Balance the order of presentation so Linux and Windows approaches are introduced together, or use tabs to separate platform-specific instructions.
- Clarify which approaches are cross-platform and which are Windows-only, to reduce confusion.
- Include troubleshooting tips for Linux users, such as file permissions and environment variable usage.
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 assignment, but PowerShell is given equal prominence, and Windows-specific certificate tooling (IIS, Certreq.exe) is mentioned before Linux alternatives. The FAQ and automation sections also reference PowerShell scripts alongside CLI, and Windows tools are referenced for certificate export. While OpenSSL is documented for Linux/macOS users, Windows-centric tools and patterns are often mentioned first or exclusively.
Recommendations
- Ensure Linux/macOS alternatives (e.g., OpenSSL) are mentioned before or alongside Windows tools like IIS and Certreq.exe for certificate export.
- Provide explicit Linux/macOS examples for certificate management tasks where PowerShell or Windows tools are referenced.
- In automation sections, clarify that Azure CLI works cross-platform and highlight it as the primary example, with PowerShell as a secondary option for Windows users.
- Where screenshots or UI instructions are given, note any OS-specific differences (if any) 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
Missing Linux Example
Summary
The documentation page covers environment variables and app settings for Azure App Service across Windows and Linux platforms. However, there is a notable Windows-first bias: Windows paths and conventions (e.g., D:\home) are frequently mentioned before Linux equivalents, and some examples and explanations use Windows-centric terminology. Several environment variables and features are described primarily or exclusively for Windows (e.g., IIS, Web Deploy/MSDeploy, machineKey, Jetty/Tomcat settings), with Linux alternatives referenced later or in separate sections. Some settings lack Linux-specific examples or details, and Windows tools (e.g., msbuild, Web Deploy) are discussed without equivalent Linux tooling. While Linux coverage exists (notably Oryx build automation and container settings), the structure and examples tend to prioritize Windows scenarios.
Recommendations
- Ensure Linux and Windows examples are presented side-by-side or in parallel, rather than Windows-first.
- Where Windows tools (e.g., msbuild, Web Deploy) are mentioned, provide Linux alternatives or clarify platform applicability.
- Add Linux-specific examples for environment variables, especially where only Windows paths or conventions are shown.
- Explicitly indicate platform applicability for each setting, and avoid assuming Windows as the default context.
- Reorganize sections to alternate or group by platform, reducing implicit prioritization of Windows.
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 and shown first, with C# and Java examples for Windows. Linux guidance is present but less prominent, with Linux examples only for C# and no code samples for other languages (Node.js, PHP, Python, Java). Windows certificate store patterns and tools are explained before Linux equivalents, and references to Windows-specific APIs and stores are more thorough.
Recommendations
- Add code examples for Linux for other popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the provided file paths.
- Present Linux and Windows examples side-by-side or in parallel tabs for all major languages, rather than focusing on Windows first.
- Expand explanations of Linux certificate handling, including common libraries (e.g., OpenSSL, cryptography) and best practices.
- Clarify when guidance applies to both platforms and highlight platform differences more explicitly.
- Reference Linux tools and patterns (e.g., environment variables, file permissions) where relevant.
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
Missing Linux Example
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there are several instances of Windows bias: Windows paths and conventions (e.g., D:\home) are often mentioned first or exclusively in examples; references to Windows tools (such as msbuild, Web Deploy/MSDeploy, IIS, and w3wp.exe) are frequent and sometimes lack Linux equivalents or explanations; some sections (e.g., Kudu build automation) are Windows-centric and presented before Linux alternatives; and some examples or settings use Windows environment variable syntax or refer to Windows-only features without always clarifying Linux differences. While Linux support is present (e.g., Oryx build automation, Linux-specific settings), parity and visibility could be improved.
Recommendations
- Ensure that examples and paths are shown for both Windows and Linux, ideally side-by-side or with clear tabs/pivots.
- When referencing Windows tools or conventions (e.g., msbuild, Web Deploy), explicitly mention Linux alternatives (e.g., Oryx, ZIP deploy) and provide links or brief explanations.
- In tables and lists, avoid listing Windows paths or features first unless they are more common; alternate ordering or use neutral language.
- Where environment variables or settings differ between Windows and Linux, clearly indicate applicability and provide Linux-specific usage notes.
- Add more Linux/macOS-focused examples, especially for deployment, logging, and build automation.
- Clarify when a feature or variable is Windows-only, Linux-only, or cross-platform, to reduce ambiguity.
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
Missing Linux Example
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a noticeable Windows-first bias: Windows paths and conventions are often mentioned before Linux equivalents, some examples and explanations use Windows-centric tools (such as msbuild, Web Deploy/MSDeploy, IIS, and Windows file paths), and certain environment variables are described primarily in the context of Windows apps. Linux-specific details are present, especially for container scenarios and Oryx build automation, but Windows terminology and examples tend to dominate or appear first. Some settings lack Linux-specific usage examples or clarifications, and references to Windows tools (like msbuild, Web Deploy, applicationHost.config) are not always balanced with Linux alternatives.
Recommendations
- Where environment variables or settings apply to both Windows and Linux, present Linux examples and paths alongside Windows ones, or alternate which is shown first.
- Add Linux-specific usage examples for settings currently described only in Windows terms (e.g., msbuild, Web Deploy, applicationHost.config).
- Clarify which settings are Windows-only, Linux-only, or cross-platform in all tables and explanations.
- For build automation, provide more detail and parity for Oryx (Linux) configuration, matching the depth given to Kudu (Windows).
- Where Windows tools are referenced, mention Linux alternatives or note their absence.
- Ensure that environment variable descriptions include both Windows and Linux paths/formats where applicable.
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
Missing Linux Example
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths (e.g., D:\home) and tools (e.g., msbuild, Web Deploy/MSDeploy, IIS) are mentioned first or exclusively in several sections. Many examples and variable descriptions use Windows conventions before Linux equivalents, and some settings reference Windows-only features without always clarifying Linux alternatives. In some cases, Linux-specific details are present but less emphasized or appear after Windows details. Some sections (e.g., Build automation) are split into Windows (Kudu) and Linux (Oryx) tabs, which helps, but Windows terminology and examples are more prevalent overall.
Recommendations
- Where environment variable paths are shown, always provide both Windows and Linux examples side-by-side (e.g., D:\home and /home).
- When referencing tools or deployment methods (e.g., msbuild, Web Deploy), clarify Linux alternatives (e.g., Oryx, ZIP deploy) and provide parity in explanation and examples.
- Ensure Linux-specific settings and behaviors are documented with equal detail and visibility as Windows ones.
- Avoid listing Windows settings or examples first unless they are more widely used; consider alternating or grouping by OS.
- For settings that are Windows-only, explicitly state so, and for cross-platform settings, clarify differences and provide examples for both.
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
Missing Linux Example
Summary
The documentation page provides extensive coverage of environment variables and app settings for Azure App Service, but exhibits several Windows-centric biases. Windows-specific paths (e.g., D:\home), tools (e.g., msbuild, Web Deploy/MSDeploy), and configuration references (e.g., applicationHost.config, IIS, w3wp.exe) are mentioned frequently and often before their Linux equivalents. Some examples and explanations default to Windows conventions, and certain sections (such as build automation and logging) provide more detail for Windows than Linux. Linux-specific options are present but less emphasized, and examples for Linux/macOS users are sometimes missing or less detailed.
Recommendations
- Ensure Linux and macOS equivalents are mentioned alongside Windows tools and paths, especially in tables and examples.
- Provide Linux/macOS-specific examples and usage patterns where Windows tools (e.g., msbuild, Web Deploy) are referenced.
- When describing environment variables, list Linux and Windows paths side-by-side (e.g., D:\home and /home).
- Clarify which settings are platform-specific and provide parity in explanation and detail for Linux features (e.g., Oryx build automation, container settings).
- Add explicit notes or tabs for Linux/macOS users where workflows or troubleshooting steps differ.
- Review sections where Windows terminology (e.g., applicationHost.config, IIS, w3wp.exe) is used and ensure Linux alternatives or limitations are described.
App Service
App Service Managed Certificate (ASMC) Changes – July 28, 2025
...e/app-service-managed-certificate-changes-july-2025.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the resource identification section, where only a PowerShell script is provided to scan for impacted Traffic Manager profiles. There is no mention of Linux/macOS alternatives (such as Bash, Azure CLI, or cross-platform scripting), and the instructions assume use of PowerShell and Windows. The PowerShell example is presented before any other tooling, and no Linux/macOS-compatible script or guidance is offered.
Recommendations
- Provide equivalent Azure CLI or Bash script examples for identifying impacted Traffic Manager profiles, ensuring Linux/macOS users can follow along without PowerShell.
- Explicitly mention cross-platform alternatives and clarify which tools work on Windows, Linux, and macOS.
- Reorder examples so that cross-platform tools (e.g., Azure CLI, REST API) are presented before or alongside PowerShell.
- Add notes or links to documentation on running PowerShell Core on Linux/macOS if PowerShell is required.
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 instructions, tools, and code samples are presented first and in greater detail, including direct use of the Windows certificate store and examples in C# and Java for Windows. Linux instructions are less detailed, often deferred to external documentation, and Linux code samples are limited to C#. There is a lack of parity for other languages (Node.js, PHP, Python, Java) on Linux, and Windows-centric patterns (certificate store, environment variables) are emphasized throughout.
Recommendations
- Provide Linux examples for popular languages such as Node.js, Python, Java, and PHP, not just C#.
- Present Windows and Linux instructions side-by-side or in parallel tabs to avoid Windows-first ordering.
- Include Linux-specific tools and patterns (e.g., OpenSSL, PEM/PFX handling) where appropriate.
- Clarify differences in certificate handling between Windows and Linux early in the document.
- Reduce reliance on Windows certificate store examples; offer equivalent Linux filesystem-based workflows.
- Ensure all critical steps (e.g., making certificates accessible, loading them in code) have Linux-specific guidance.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal. Azure PowerShell is featured as a primary method for several tasks, but there are no explicit Linux/macOS shell examples (e.g., Bash, zsh) or references to Linux-specific tools. The order of presentation often puts Azure CLI first, but PowerShell is given parity, and there are no platform-specific command-line examples (such as Bash scripts or Linux FTP clients). There is a note about escaping the dollar sign in Bash, but no concrete Linux shell commands are shown. The absence of Linux/macOS-specific instructions or examples may create friction for non-Windows users.
Recommendations
- Add explicit Bash/zsh shell examples for credential management and deployment, especially for local Git and FTP/S operations.
- Include references to common Linux/macOS tools (e.g., curl, lftp, git) for deployment and credential usage.
- Clarify cross-platform compatibility for Azure CLI commands and note any differences in behavior or prerequisites on Linux/macOS.
- Provide troubleshooting tips for Linux/macOS users, especially regarding authentication and credential formatting.
- Balance the presentation order so that Linux/macOS examples are shown alongside or before Windows/PowerShell examples where relevant.