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 1351-1375 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 provides both Azure CLI and Azure PowerShell examples for automating certificate operations, but PowerShell is mentioned equally or slightly more prominently. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, while Linux tools (OpenSSL) are also covered. However, Windows tools are mentioned first in some sections and the PowerShell example is given alongside the CLI example, which may create friction for Linux/macOS users. There are no critical sections that are Windows-only, and Linux-friendly instructions (OpenSSL, Azure CLI) are present.
Recommendations
- Ensure Azure CLI examples are always given before PowerShell, as CLI is cross-platform.
- Where Windows tools (IIS, Certreq.exe) are mentioned, provide equivalent Linux/macOS instructions or clarify that OpenSSL is the preferred cross-platform method.
- Explicitly state which steps are platform-agnostic and which are Windows-specific.
- Add links or brief instructions for certificate export on Linux/macOS, if not already present.
- Consider grouping automation examples by platform, with Linux/macOS first, to improve parity.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides Azure portal and Azure CLI instructions, which are cross-platform, but there are several subtle Windows biases. Windows file paths and environment variables (e.g., `%HOME%`, `D:\home\site\wwwroot\`) are used as primary examples, and the Kudu DebugConsole is referenced with Windows-style paths. FTP upload instructions reference Windows directories. The mention of Azure PowerShell is prominent, and PowerShell samples are linked alongside CLI samples, but no Bash or Linux shell samples are provided. Windows terminology and patterns (such as `%HOME%` and drive letters) appear before Linux equivalents, and screenshots and examples are Windows-centric.
Recommendations
- Provide Linux/macOS equivalents for file paths and environment variables (e.g., `/home/site/wwwroot` instead of `D:\home\site\wwwroot\`).
- Add Bash or Linux shell sample scripts alongside Azure PowerShell samples.
- Clarify that Kudu DebugConsole and FTP can be used from any OS, and show Linux/macOS examples for uploading files.
- When referencing environment variables or paths, mention both Windows and Linux formats.
- Ensure screenshots and instructions are not Windows-exclusive, or provide Linux screenshots 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
Summary
The documentation page covers environment variables and app settings for Azure App Service, which supports both Windows and Linux. However, there are several areas where Windows-specific tools, paths, and terminology are presented first or exclusively, such as references to Windows directory paths (e.g., D:\home), IIS, Web Deploy/MSDeploy, and legacy Windows build automation (Kudu) being described before Linux equivalents (Oryx). Some settings and examples use Windows conventions or tools without always providing Linux alternatives or parity. Linux-specific information is present but often secondary.
Recommendations
- Ensure Linux paths and conventions are presented alongside Windows examples, not as an afterthought.
- Where Windows tools (e.g., Web Deploy, MSDeploy, IIS) are mentioned, clarify their Linux equivalents or note if not applicable.
- Present Linux build automation (Oryx) and deployment options equally, and not only in secondary tabs.
- Add explicit Linux/macOS examples for environment variable usage, especially where Windows paths or tools are referenced.
- Review tables and descriptions to ensure Linux-specific settings are not buried or omitted.
- Where possible, use neutral language and examples that apply to both platforms, or clearly indicate platform-specificity.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for Azure CLI, PowerShell, ARM templates, and portal instructions for managing identities in Azure App Service and Functions. However, PowerShell examples are prominent and often shown alongside or before CLI examples, and PowerShell is referenced in a way that may imply Windows environments. There are no explicit Linux/macOS-specific instructions or clarifications, and PowerShell is not flagged as cross-platform. Azure CLI is available on all platforms, but PowerShell instructions may create friction for Linux/macOS users unfamiliar with it.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or link to installation instructions for Linux/macOS.
- Ensure Azure CLI examples are shown first or equally with PowerShell, as CLI is more commonly used on Linux/macOS.
- Add explicit notes or links for Linux/macOS users, e.g., 'Azure CLI works on Linux/macOS; see installation instructions.'
- Where PowerShell is used, note that Bash or shell scripting alternatives exist for Linux/macOS.
- Consider adding Bash shell script examples for token retrieval, especially in sections where only PowerShell is shown.
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 less prominent, with Linux-specific code examples only for C# and no explicit examples for Node.js, PHP, Python, or Java. Windows tools and patterns (certificate store, environment variables, user profile loading) are discussed more thoroughly, and Linux instructions are often deferred to external language/platform documentation.
Recommendations
- Add explicit Linux code examples for Node.js, PHP, Python, and Java, showing how to load certificates from the Linux file paths provided.
- Present Linux and Windows guidance in parallel sections or tabs, rather than Windows-first.
- Expand Linux-specific instructions to match the detail given for Windows, including environment variable usage and certificate file handling.
- Clarify any differences in certificate handling between Linux and Windows, especially for containerized workloads.
- Where possible, avoid referring Linux users to external documentation; provide at least basic sample code inline.
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 RBAC assignment, but PowerShell is featured equally and referenced in several places. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned for exporting certificates, while Linux tools (OpenSSL) are also included. However, Windows tools are referenced before Linux equivalents in some sections, and PowerShell is given equal prominence to Azure CLI. There are links to Windows Server documentation for certificate export, but no explicit Linux/macOS export guidance. Overall, the bias is moderate, with Windows tools and patterns mentioned alongside but sometimes before Linux equivalents.
Recommendations
- Add explicit Linux/macOS guidance for exporting certificates (e.g., OpenSSL usage for certificate requests and exports).
- Ensure Linux/OpenSSL instructions are presented before or alongside Windows/IIS/Certreq.exe instructions, not after.
- Where PowerShell is used, always provide Azure CLI equivalents and highlight cross-platform options.
- Link to Linux/macOS documentation for certificate management/export, not just Windows Server docs.
- Clarify that Azure CLI is cross-platform and encourage its use for non-Windows 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 covers environment variables and app settings for Azure App Service, supporting both Windows and Linux. However, there is a notable Windows bias: Windows-specific paths (e.g., 'D:\home'), tools (e.g., msbuild, Web Deploy/MSDeploy), and IIS-related settings are often mentioned first or exclusively. Windows terminology and examples (such as `%HOME%` and `.dll` extensions) appear before or instead of Linux equivalents. While Linux-specific variables and sections exist (e.g., Oryx build automation, Linux container settings), Windows settings and tools are more prominently described, and Linux examples are sometimes missing or less detailed.
Recommendations
- Ensure Linux paths and equivalents are mentioned alongside Windows paths in all examples and tables.
- Provide Linux-specific examples and explanations where Windows tools (e.g., msbuild, Web Deploy) are referenced.
- Balance the order of presentation so Linux and Windows are treated equally (e.g., list both '/home' and 'D:\home' for HOME variable).
- Expand Linux build automation (Oryx) documentation to match the detail given for Windows (Kudu).
- Clarify which settings are Windows-only and which are cross-platform, ideally with clear labels or pivots.
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 are several instances where Windows-specific tools, paths, and conventions are mentioned first or exclusively, such as referencing Windows directory paths (e.g., D:\home), IIS, and Windows-specific environment variables. Some examples and explanations use Windows-centric terminology or tools (e.g., msbuild, Web Deploy/MSDeploy, applicationHost.config) without always providing Linux equivalents or parity. While Linux-specific sections (Oryx, Linux containers) are present, Windows examples and tools are often listed first or in greater detail. Some settings are described with Windows paths or behaviors, and Linux alternatives are not always equally explained.
Recommendations
- Ensure Linux examples and paths are provided alongside Windows examples, especially for environment variables referencing file paths.
- When mentioning Windows tools (e.g., msbuild, Web Deploy/MSDeploy), provide Linux alternatives or clarify if the feature is Windows-only.
- Balance the order of presentation so Linux and Windows are equally represented, or use neutral language where possible.
- Expand explanations for Linux-specific build automation (Oryx) and deployment scenarios to match the detail given for Windows/Kudu.
- Add explicit notes or tables indicating which settings are platform-specific, and provide links to Linux documentation where relevant.
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 featured equally and referenced in automation FAQs. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. Windows-specific export instructions are given, and PowerShell is listed alongside CLI for automation, but Linux alternatives are not always equally explained or referenced first.
Recommendations
- Provide Linux/macOS-specific instructions and examples wherever Windows tools (IIS, Certreq.exe, PowerShell) are mentioned, such as for certificate export.
- Ensure OpenSSL instructions are as detailed as Windows tool instructions, including troubleshooting and compatibility notes.
- Feature Azure CLI examples before PowerShell, as CLI is cross-platform.
- Add explicit guidance for Linux/macOS users in automation sections, including shell scripting and certificate management.
- Where screenshots or UI steps reference Windows-specific terminology, clarify that the steps are identical for Linux-hosted apps.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform, describing App Service plans for both Windows and Linux. However, the Managed Instance section is Windows-only and presented without a Linux equivalent or alternative. Additionally, some links and feature tables (such as pricing details) default to Windows, and there are no Linux-specific examples or guidance for Linux users, which may create friction for those seeking parity.
Recommendations
- Clearly label Windows-only features (such as Managed Instance) and provide guidance or alternatives for Linux users where possible.
- Include links to Linux-specific documentation (e.g., App Service on Linux pricing details, feature support matrix).
- Add examples or notes for Linux App Service plans, especially where feature availability or configuration differs.
- Ensure that feature tables and plan comparisons explicitly state OS applicability, and avoid defaulting to Windows unless the feature is truly Windows-only.
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 demonstrates a moderate Windows bias. Windows-specific instructions 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# for Linux. Non-Windows languages (Node.js, PHP, Python, Java) are not covered with direct examples for Linux, and users are referred to external documentation. Windows certificate store patterns and tools are described in detail, while Linux approaches are less emphasized.
Recommendations
- Provide direct code examples for Linux for all major supported languages (Node.js, Python, Java, PHP), not just C#.
- Present Linux and Windows instructions/examples in parallel or with equal prominence, rather than Windows-first.
- Clarify any differences in certificate handling between Windows and Linux up front.
- Include more detailed guidance for Linux users on best practices for certificate storage and access.
- Where possible, avoid referring Linux users to external documentation for basic tasks that are explained in detail for Windows.
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 tools (IIS, Certreq.exe) are mentioned for certificate export, while Linux alternatives are not described in detail. Windows-specific certificate generation/export methods are referenced before Linux/OpenSSL equivalents in some sections. However, OpenSSL is covered for Linux/macOS users, and Azure CLI is included for automation. The overall bias is moderate, with some friction for Linux/macOS users but no critical gaps.
Recommendations
- Ensure Linux/macOS certificate export instructions (using OpenSSL) are as detailed and prominent as Windows/IIS instructions.
- Where PowerShell is referenced, always provide equivalent Azure CLI or Bash examples, and consider showing CLI first.
- Clarify that OpenSSL steps are suitable for Linux/macOS, and link to official OpenSSL documentation for further guidance.
- Add troubleshooting tips for Linux/macOS users, such as handling certificate chain issues or .pfx compatibility.
- Review FAQ and automation sections to ensure Linux/macOS parity in scripting guidance.
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 demonstrates a moderate Windows bias. Windows-specific instructions and code samples (especially for certificate loading) are presented first and in greater detail, with C# and Java examples focused on the Windows certificate store. Linux-specific guidance is less prominent and less detailed, with non-Windows languages (Node.js, PHP, Python) being deferred to external documentation. The use of Windows tools and patterns (certificate store, environment variables) is emphasized, and Linux parity is only partially addressed.
Recommendations
- Provide Linux-specific code samples for all supported languages (e.g., Java, Python, Node.js, PHP) directly in the documentation, not just C#.
- Present Windows and Linux instructions/examples in parallel or in clearly separated tabs, rather than Windows-first.
- Expand explanations of Linux certificate handling, including how to access certificates from the file system in common languages.
- Clarify any differences in certificate management between Windows and Linux environments up front.
- Link to or include sample scripts for Linux shell (bash) where relevant, not just Azure CLI or PowerShell.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a general overview of Azure App Service plans, mentioning both Windows and Linux as supported operating systems. However, in the 'Managed Instance on Azure App Service (preview)' section, the examples and features are exclusively Windows-focused, with no Linux equivalent or parity. Additionally, links such as 'App Service plan details' point to Windows-specific pricing by default, and there are no Linux-specific examples or guidance throughout the page.
Recommendations
- Add explicit examples and guidance for Linux-based App Service plans, including supported features, pricing, and scaling considerations.
- Where features are Windows-only (such as Managed Instance), clearly label them as such and provide links or notes about Linux alternatives or limitations.
- Ensure that documentation links (e.g., pricing details) reference both Windows and Linux options, or clarify when a link is Windows-specific.
- Include parity tables or comparison charts that show which features are available on Windows vs. Linux App Service plans.
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 (e.g., D:\home), tools (e.g., msbuild, Web Deploy/MSDeploy), and references (e.g., IIS, applicationHost.config) are frequently mentioned first or exclusively. Windows-centric terminology and examples (such as referencing Windows time zones, Windows container settings, and legacy Windows build automation via Kudu) appear before or more prominently than Linux equivalents. Linux-specific details (such as Oryx build automation, Linux container settings, and Linux paths) are present but often secondary or less detailed.
Recommendations
- Ensure Linux examples and paths (e.g., /home) are shown alongside Windows paths, not just in parentheses.
- Present Linux build automation (Oryx) and deployment options with equal prominence to Windows/Kudu/MSDeploy.
- Where Windows tools or settings are referenced (e.g., msbuild, Web Deploy), provide Linux alternatives or clarify applicability.
- Where possible, list Linux and Windows settings in parallel tables or sections, rather than Windows-first.
- Expand Linux-specific documentation (e.g., for custom containers, logging, caching, and build automation) to match Windows detail.
- Avoid referencing Windows-only features (e.g., applicationHost.config, IIS) in general sections unless clearly marked as Windows-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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific certificate store access is covered in detail with C# and Java examples, while Linux guidance is limited to file-based access and only C# examples are provided. Non-Windows languages (Node.js, PHP, Python, Java) are referenced but not exemplified. Windows certificate store tools and patterns are discussed first and more thoroughly, with Linux instructions appearing later and less prominently.
Recommendations
- Add explicit Linux examples for accessing certificates in popular languages (Node.js, Python, Java, PHP) using file paths and environment variables.
- Present Linux and Windows guidance in parallel sections, rather than Windows-first.
- Expand Linux guidance to include common certificate management patterns and troubleshooting.
- Clarify that file-based access is the primary method for Linux, and provide code samples for multiple languages.
- Mention Linux environment variables for certificate paths earlier and more prominently.
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 RBAC assignment, but PowerShell is given equal prominence and referenced in automation FAQs. Windows-specific certificate tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. Windows tools are mentioned before Linux equivalents, and PowerShell is featured alongside CLI, which may create friction for Linux/macOS users.
Recommendations
- Ensure all automation and scripting examples are provided for Azure CLI first, as it is cross-platform, and PowerShell second.
- Expand instructions for certificate export using OpenSSL, including guidance for both Linux and macOS users.
- Add explicit guidance for exporting certificates on Linux/macOS, avoiding references to Windows-only tools unless necessary.
- Where Windows tools are mentioned (IIS, Certreq.exe), provide equivalent Linux/macOS instructions or links.
- In FAQs and automation sections, highlight Azure CLI as the primary method for cross-platform 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 platforms, but exhibits a moderate Windows bias. Windows-specific paths, tools, and configuration patterns are often mentioned first or exclusively (e.g., use of D:\home, references to IIS, applicationHost.config, and .bat files). Some examples and descriptions use Windows-centric syntax or refer to Windows-only tools (e.g., msbuild, Web Deploy/MSDeploy, w3wp.exe) without always providing Linux equivalents or clarifying platform differences. Linux-specific details are sometimes present but less prominent or detailed.
Recommendations
- For every Windows-specific path or example (e.g., D:\home), provide the Linux equivalent (/home) alongside.
- When referencing Windows tools (e.g., msbuild, Web Deploy), explicitly state their Linux alternatives or clarify if not applicable.
- Ensure that Linux and macOS examples are provided with equal prominence, especially in sections like deployment, logging, and build automation.
- Where platform-specific variables or behaviors exist, clearly label them as such and provide parity in documentation depth.
- Add more Linux/macOS-focused troubleshooting notes and usage patterns where only Windows ones are currently present.
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, language-specific examples (C#, Java) for loading certificates in Windows apps and containers, including use of the Windows certificate store and related APIs. Linux guidance is limited to generic file loading, with only C# examples for Linux containers. For other languages (Node.js, PHP, Python, Java), Linux users are referred to external documentation, while Windows users get in-page code samples. Windows-specific tools and patterns (certificate store, environment variables) are discussed first and in more depth.
Recommendations
- Add Linux-specific code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from file paths in Linux containers.
- Provide parity in guidance for Linux apps, including how to handle certificate permissions, file formats, and environment variables.
- Reorganize sections so Linux and Windows guidance are presented side-by-side or equally, rather than Windows-first.
- Clarify that some Windows-specific APIs (like certificate store access) are not available on Linux, and offer Linux alternatives.
- Expand the 'Load a certificate from a file' section with concrete Linux examples for multiple languages.
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 mentioned and shown as a primary option in several places. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, and Windows tooling is mentioned before Linux equivalents. While OpenSSL is covered for Linux/macOS users, Windows export instructions are more detailed and linked. The FAQ and automation sections also highlight PowerShell scripts alongside CLI, but do not provide Bash or Linux-native scripting examples. Overall, Linux users can complete all tasks, but Windows tools and patterns are more prominent.
Recommendations
- Provide Linux/macOS-specific instructions and examples alongside Windows tools (e.g., show Bash scripting for automation, not just PowerShell).
- Ensure OpenSSL instructions are as detailed as Windows export instructions, including troubleshooting and password management.
- Mention Linux-native certificate management tools (such as certbot or keytool) where relevant, or clarify their applicability.
- When referencing automation, include Bash/CLI scripts as first-class options, not just PowerShell.
- Balance the order of examples so Linux/CLI instructions are not always after Windows/PowerShell.
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, tools, and terminology (e.g., 'D:\home', IIS, msbuild, Web Deploy/MSDeploy, site extensions, .bat files, Windows container settings) are often mentioned first or exclusively. Some examples and explanations use Windows conventions without always providing Linux equivalents. While Linux-specific sections (Oryx, Linux containers, language runtimes) are present, Windows-centric information is more prominent and detailed, and Linux examples or explanations are sometimes missing or less thorough.
Recommendations
- Ensure all environment variable examples include both Windows and Linux paths/formats (e.g., 'D:\home' and '/home').
- Where Windows tools (e.g., msbuild, Web Deploy/MSDeploy, .bat files) are mentioned, provide Linux alternatives or clarify applicability.
- Present Linux and Windows information in parallel, rather than Windows-first (e.g., in tables, list both OSes or use tabs).
- Expand Linux-specific explanations and examples, especially for deployment, logging, and build automation.
- Clarify when a variable or feature is Windows-only, Linux-only, or cross-platform.
- Add more Linux-specific troubleshooting, paths, and tool references where appropriate.
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 notable Windows bias. Windows-specific instructions, code samples, and certificate store usage are presented first and in greater detail, including C# and Java examples for accessing the Windows certificate store. Linux equivalents are either deferred, less detailed, or referenced generically (e.g., 'see the documentation for the respective language'). Linux-specific code samples are limited to C# file loading, with no Node.js, Python, PHP, or Java examples. Windows tools and patterns (certificate store, thumbprint usage, environment variables) are emphasized, while Linux approaches are less thoroughly explained.
Recommendations
- Provide Linux examples for all major languages (Node.js, Python, PHP, Java), not just C#.
- Present Linux and Windows instructions/examples in parallel tabbed sections, rather than Windows-first.
- Expand Linux-specific guidance on certificate handling, including common pitfalls and best practices.
- Reference Linux tools and patterns (e.g., OpenSSL, file permissions) where relevant.
- Clarify when instructions are Windows-only and provide direct Linux alternatives where possible.
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 RBAC role assignment, but PowerShell is given equal prominence and referenced in several places. Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, with only a brief reference to OpenSSL for Linux/macOS users. The PowerShell example is shown directly after the CLI example, and Windows tools are mentioned before Linux equivalents in the certificate export section. There are no Linux/macOS-specific portal screenshots or explicit parity checks for non-Windows users.
Recommendations
- Expand the certificate export section with explicit Linux/macOS instructions, including OpenSSL commands and troubleshooting tips.
- Add more detailed examples for Linux/macOS users, such as using OpenSSL for certificate requests and exports, and clarify any differences in portal experience.
- Where PowerShell is referenced, ensure Azure CLI examples are equally prominent and provide Bash scripting examples for automation.
- Mention Linux/macOS tools before or alongside Windows tools when discussing certificate generation and export.
- Add notes or links for Linux/macOS users regarding certificate management best practices.
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 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 tools, paths, and conventions are mentioned first or exclusively, such as referencing Windows directory paths (e.g., D:\home), IIS, Web Deploy/MSDeploy, and legacy Windows build automation (Kudu) before Linux equivalents (Oryx). Some examples and explanations default to Windows terminology, and Windows-specific settings are often described in greater detail. Linux-specific settings are present but sometimes appear as afterthoughts or are less thoroughly documented.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows examples, especially for directory paths, deployment, and logging.
- Where possible, present Linux and Windows information in parallel, rather than defaulting to Windows-first descriptions.
- Expand Linux-specific documentation (e.g., Oryx build automation, Linux container settings) to match the detail provided for Windows/Kudu.
- Clarify which settings are platform-specific and provide clear guidance for Linux/macOS users.
- Avoid referencing Windows tools (e.g., IIS, MSDeploy) without mentioning Linux alternatives or noting their applicability.
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 patterns are presented first and in greater detail, including both C# and Java code for accessing certificates from the Windows certificate store. Linux guidance is less prominent, with Linux-specific code examples only shown for C# and only in the container section. There are no direct Linux examples for Java, Node.js, PHP, or Python, and users of those platforms are referred to external documentation. Windows-specific tools and environment variables are described before their Linux equivalents.
Recommendations
- Add Linux-specific code samples for Java, Node.js, PHP, and Python, demonstrating how to load certificates from the Linux file system paths provided.
- Present Linux and Windows examples side-by-side or in parallel tabs throughout the documentation, rather than focusing on Windows first.
- Include explicit instructions for accessing certificates in Linux App Service apps (not just containers), especially for popular languages.
- Clarify any platform-specific limitations or differences in certificate handling between Windows and Linux.
- Reference Linux tools and patterns (such as OpenSSL, environment variables, etc.) where appropriate.