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 1076-1100 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell automation example but omitting equivalent Linux/bash scripting examples. The scripting section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no bash or Linux shell script provided. There is also a subtle 'windows_first' ordering, as PowerShell is highlighted and the ms.custom metadata references Azure PowerShell. No Linux-specific tools or workflows are mentioned, and Linux automation is not given equal prominence.
Recommendations
- Provide a bash/Linux shell script example for automating certificate binding, similar to the PowerShell example.
- Ensure that Azure CLI examples are shown inline and not just linked, giving them parity with PowerShell.
- Avoid listing PowerShell before bash/Azure CLI unless there is a technical reason; consider alternating or grouping by platform.
- Add explicit notes or sections for Linux users, especially in automation and scripting contexts.
- Review metadata (such as ms.custom) to ensure it does not reinforce a Windows/Powershell-centric approach.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but there are no Bash or Linux shell equivalents for PowerShell commands. Outbound IPv6 support is explicitly stated as available only for Windows apps, with no Linux parity. The documentation references Windows-specific tools and patterns (PowerShell, Azure PowerShell module) without offering Linux-native alternatives or clarifying cross-platform compatibility. In some sections, Windows/PowerShell examples are given before or instead of Linux/Bash examples.
Recommendations
- For every Azure PowerShell example, provide a Bash/Linux shell equivalent (e.g., using Azure CLI or REST API with curl).
- Clarify in all relevant sections whether commands and features are cross-platform, and if not, provide Linux-specific guidance or workarounds.
- Explicitly state the lack of outbound IPv6 support for Linux apps and provide a roadmap or alternatives if possible.
- When listing command examples, alternate the order or group them by platform, rather than defaulting to Windows/PowerShell first.
- Reference Linux-native tools (e.g., dig, curl, jq) where appropriate, especially in sections about DNS or IP address lookup.
- Add a table or section summarizing feature parity and differences between Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While the main workflow is described via the Azure Portal (which is cross-platform), the automation section lists PowerShell before Azure CLI, and only the PowerShell script is shown inline, with no equivalent Bash or Linux shell example. There is no mention of Linux-specific tools or workflows for uploading certificates or managing bindings, and the only explicit code sample is for PowerShell. The only nod to Linux is an indirect reference to a 'Linux Node.js configuration' guide in the FAQ, but no Linux command-line or scripting examples are provided on this page.
Recommendations
- Provide Bash or Linux shell script examples alongside PowerShell in the automation section, or at least link to them.
- List Azure CLI examples before or alongside PowerShell to avoid the appearance of Windows-first bias.
- Include explicit instructions or references for Linux users when uploading certificates (e.g., how to generate or upload .pfx files from Linux).
- Ensure that all code samples have both Windows (PowerShell) and Linux (Bash/CLI) equivalents.
- Mention any platform-specific considerations (such as file paths or certificate handling differences) where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no explicit Linux shell or Bash alternatives for PowerShell commands. The outbound IPv6 support section specifically notes that outbound IPv6 is only available for Windows apps, with Linux apps limited to IPv4. In several places, PowerShell is presented as a primary or co-equal method, but Linux-native tools or scripts are not mentioned. There is also a lack of explicit mention of Linux environments or tools, and the documentation does not clarify cross-platform compatibility for all commands.
Recommendations
- For every PowerShell example, provide an equivalent Bash or Linux-native command (e.g., using Azure CLI in Bash, or REST API with curl).
- Clarify in each code example which platforms are supported (e.g., 'This PowerShell command is for Windows; use Azure CLI for cross-platform').
- Where outbound IPv6 is Windows-only, explicitly state this in summary tables and provide a roadmap or workaround for Linux users.
- Add a section or callout summarizing cross-platform support for all commands and features discussed.
- Ensure that Linux users are not required to use PowerShell for any management tasks; always provide a CLI or REST alternative.
- Where the Azure portal is referenced, clarify that it is platform-agnostic.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. It prioritizes ASP.NET and ASP.NET Web Forms (Windows-centric frameworks) in its code samples, providing them before cross-platform or Linux-native frameworks. There is no mention of Linux-specific tools or shell commands (e.g., Bash, OpenSSL) for certificate management or validation. The Azure CLI example is cross-platform, but there are no Linux-specific configuration or troubleshooting examples, and the overall structure and sample order favor Windows development patterns.
Recommendations
- Add Linux shell (Bash) and OpenSSL examples for certificate inspection and validation.
- Include troubleshooting steps or notes for common Linux client/server environments (e.g., NGINX, Apache).
- Provide parity in sample order: present cross-platform (Node.js, Java, Python) or Linux-native frameworks before or alongside Windows-centric ones.
- Mention and link to Linux tools for certificate management (e.g., OpenSSL, certbot) where relevant.
- Clarify that the Azure CLI commands work identically on Linux, macOS, and Windows.
- If possible, add a section or tab for configuring mutual TLS in Linux-based App Service containers (e.g., Dockerfile or startup script examples).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are given equal prominence to CLI, and there is no explicit mention of Linux-specific tools or workflows. The only non-Azure tool example is 'nslookup', which is cross-platform, but there are no Linux shell or scripting examples (e.g., Bash, grep, jq). Additionally, outbound IPv6 support is noted as being available only for Windows apps, with no Linux parity. The documentation does not mention Linux-specific considerations or provide Linux-first examples.
Recommendations
- Provide Linux/Bash-native examples alongside or before PowerShell, such as using jq with az CLI output.
- Clarify that Azure CLI commands work cross-platform and highlight usage in Bash or other Linux shells.
- Explicitly mention the lack of outbound IPv6 support for Linux apps and provide a roadmap or workaround if possible.
- Include Linux-specific troubleshooting or verification steps (e.g., using dig, curl, or ip commands).
- Where PowerShell is shown, add equivalent Bash or shell scripting examples to ensure Linux users are equally supported.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell in the automation section and not providing Linux-specific or cross-platform CLI examples inline. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is directly embedded, with no equivalent Bash or Linux shell example. There are no explicit Linux or macOS workflow instructions, and the documentation does not mention Linux tools or provide parity in example scripts.
Recommendations
- Include inline Azure CLI (cross-platform) script examples alongside or before PowerShell examples in the 'Automate with scripts' section.
- Provide explicit instructions or notes for Linux/macOS users, especially for certificate upload steps (e.g., how to generate or convert .pfx files on Linux).
- Ensure that any referenced scripts or automation workflows are available in both PowerShell and Bash (or at least Azure CLI) formats.
- Add links or references to Linux-specific documentation or troubleshooting guides where relevant.
- Review screenshots and UI instructions to ensure they are not Windows-specific and clarify any platform-agnostic steps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, particularly in the application code samples and terminology. The .NET/ASP.NET (Windows-centric) examples are presented first and in greater detail, with explicit references to Windows-specific properties and patterns. There is a lack of Linux shell or OpenSSL command-line examples for certificate management, and the documentation assumes the use of Azure Cloud Shell (which is cross-platform but often defaults to PowerShell). The focus on .NET and Windows-native certificate handling precedes or outweighs coverage of Linux-native approaches.
Recommendations
- Add explicit Linux command-line examples (e.g., using bash and OpenSSL) for generating, inspecting, and handling client certificates.
- Include examples for configuring mutual TLS in popular Linux web servers (such as Nginx and Apache) in addition to .NET/ASP.NET.
- Clarify that the Azure CLI can be used from any platform, and provide bash/zsh syntax where appropriate.
- Balance the order of code samples so that Linux-friendly stacks (Node.js, Python, Java) are not always after Windows/.NET examples.
- Mention Linux-native certificate stores and tools (such as update-ca-certificates, certutil, or OpenSSL) where relevant.
- Where possible, provide parity in troubleshooting and validation steps for both Windows and Linux environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the automation section, where both Azure CLI and PowerShell are mentioned, but only a PowerShell script is directly embedded and shown. There are no explicit Linux shell (bash) examples or references to Linux-native tools. The documentation does not provide parity in scripting examples for Linux users, and the PowerShell script is highlighted more prominently than the Azure CLI link. Additionally, the use of .pfx files (a Windows-centric certificate format) is mentioned without referencing Linux-friendly alternatives or conversion steps.
Recommendations
- Add explicit bash or shell script examples for Linux users in the automation section, alongside PowerShell.
- Embed or link to Azure CLI scripts as prominently as PowerShell scripts.
- Mention Linux-native certificate formats (such as .pem) and provide guidance or links on converting between .pfx and .pem.
- Ensure that any references to tools or workflows (such as uploading certificates) include Linux command-line equivalents or instructions.
- Review screenshots and UI instructions to ensure they are not overly Windows-centric, and add notes for Linux/macOS users where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by featuring PowerShell as the only script example in the 'Automate with scripts' section, with no equivalent Bash or Linux shell example. The automation section lists Azure CLI and PowerShell, but only provides an inline code block for PowerShell, not for CLI or Bash. There are no Linux-specific instructions or screenshots, and the overall flow assumes use of the Azure Portal or Windows-centric tools.
Recommendations
- Add Bash or Linux shell script examples alongside PowerShell in the 'Automate with scripts' section.
- Provide explicit Azure CLI command examples inline, not just as links.
- Include Linux-specific notes or screenshots where relevant, especially for certificate upload or file path conventions.
- Ensure parity in automation instructions by presenting Windows and Linux approaches side by side.
- Reference Linux and macOS environments in prerequisites and troubleshooting sections.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. The only platform-specific examples for accessing the client certificate in application code are for ASP.NET Core and ASP.NET Web Forms, both of which are traditionally Windows-centric frameworks. The initial mention of how to access the client certificate property is for ASP.NET, with Linux/Unix-agnostic stacks (Node.js, Java, Python) following. There are no explicit Linux shell or configuration examples, and the document does not mention Linux-specific tools or patterns for certificate handling. The Azure CLI and Bicep/ARM examples are cross-platform, but the application code samples and the ordering of explanations favor Windows-first technologies.
Recommendations
- Add explicit Linux/Unix shell (bash) examples for enabling client certificates using Azure CLI, including usage from a Linux terminal.
- Include examples for popular Linux web servers (e.g., Nginx, Apache) on how to forward client certificates to the application, especially for self-hosted scenarios.
- Provide parity in application code samples by including examples for popular Linux-first frameworks (e.g., FastAPI for Python, Spring Boot for Java, Express for Node.js) and clarify any OS-specific differences.
- Reorder the 'Access the client certificate' section to mention cross-platform approaches (e.g., via HTTP headers) before Windows-specific frameworks.
- Explicitly state that the Azure CLI and Bicep/ARM approaches are cross-platform and can be used from Linux, macOS, and Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell scripting in the 'Automate with scripts' section and referencing Azure CLI only as a link, without providing direct Linux/Unix shell examples or parity in scripting walkthroughs. The page also lacks explicit Linux or cross-platform command-line instructions, and the scripting focus is on Windows tools and patterns.
Recommendations
- Provide direct Azure CLI command examples inline, not just as links, to ensure parity with PowerShell examples.
- Include Linux/Unix shell (bash) scripting examples for certificate upload and binding operations.
- Explicitly mention that the steps can be performed on both Windows and Linux, and clarify any platform-specific differences.
- Add references or links to Linux-specific documentation where relevant, such as using OpenSSL to generate .pfx files.
- Ensure that automation and scripting sections always include both PowerShell and CLI/bash examples side by side.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell automation example but omitting equivalent Linux shell (Bash) examples. The scripting section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no Bash or Linux-specific automation guidance. Additionally, there is no mention of Linux tools or workflows for certificate management, and the documentation does not provide parity in step-by-step examples for Linux users.
Recommendations
- Add Bash/Linux shell script examples for automating certificate binding, alongside PowerShell.
- Provide explicit guidance or links for Linux users on how to generate and upload certificates (e.g., using OpenSSL).
- Ensure that automation and scripting sections always include both Windows (PowerShell) and Linux (Bash/CLI) examples, or clearly indicate parity.
- Reference Linux-specific documentation or workflows where relevant, especially in sections discussing application code or certificate management.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving outbound IP addresses, but PowerShell examples are given equal prominence to CLI, and there are no explicit Linux shell or Bash script examples beyond the use of Azure CLI. The documentation references 'Cloud Shell' without clarifying that it supports both Bash and PowerShell, and does not provide Linux-native alternatives for PowerShell commands. Additionally, outbound IPv6 support is noted as being available only for Windows apps, with no Linux parity.
Recommendations
- Clearly indicate when examples are cross-platform (e.g., Azure CLI) and when they are Windows-specific (e.g., PowerShell).
- Provide explicit Bash or Linux-native command examples where possible, especially for common tasks like retrieving IP addresses.
- When referencing 'Cloud Shell', clarify that both Bash and PowerShell environments are available and show equivalent commands for each.
- If a feature (such as outbound IPv6 support) is Windows-only, explicitly mention the lack of Linux support and provide a roadmap or workaround if possible.
- Avoid giving PowerShell examples equal prominence to CLI unless there is a clear need; prioritize cross-platform tools like Azure CLI.
- Add a table or section summarizing command-line options for Windows (PowerShell), Linux (Bash), and cross-platform (Azure CLI) to improve parity and clarity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the automation section by providing a PowerShell script directly in the main content, while the Azure CLI (cross-platform) automation is only linked and not shown inline. There is no mention of Linux-specific tools or workflows, and no Linux shell (bash) examples are provided. The documentation also references PowerShell before the CLI, reinforcing a Windows-first approach.
Recommendations
- Provide inline Azure CLI and bash examples alongside PowerShell scripts in the automation section.
- Ensure that Linux and cross-platform workflows are mentioned and demonstrated equally, not just linked.
- Explicitly mention that all steps can be performed from Linux/macOS using the Azure CLI, and provide sample commands.
- Where relevant, include screenshots or instructions from both Windows and Linux environments.
- Avoid listing PowerShell or Windows-specific tools before their cross-platform or Linux equivalents.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell scripting in the 'Automate with scripts' section, referencing Azure CLI only as a link (without inline examples), and omitting explicit Linux or Bash scripting examples. The only code sample shown is PowerShell, which is more familiar to Windows users. While there is a brief mention of a Linux Node.js configuration guide, the main automation and scripting guidance is Windows-centric.
Recommendations
- Provide inline Azure CLI examples alongside PowerShell, not just as links, to ensure parity for Linux and cross-platform users.
- Include Bash scripting examples for certificate upload and binding, especially for common Linux workflows.
- When referencing automation, present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell-only.
- Expand the 'Automate with scripts' section to explicitly mention and demonstrate Linux-compatible tools and commands.
- Review screenshots and UI instructions to ensure they are not overly tailored to Windows environments (e.g., file dialogs, path formats).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias primarily by focusing on .NET/ASP.NET (Windows-centric frameworks) in code samples, providing detailed Windows/ASP.NET examples before other platforms, and referencing Windows-specific concepts (such as the HttpRequest.ClientCertificate property and .NET middleware) without equivalent Linux/Unix-native patterns. There is no mention of Linux command-line tools (e.g., OpenSSL) for certificate handling, and the overall structure assumes familiarity with Windows development environments.
Recommendations
- Add Linux/Unix-native command-line examples (e.g., using OpenSSL) for generating and inspecting client certificates.
- Include examples or references for configuring mutual TLS in popular Linux web servers (e.g., Nginx, Apache) when running App Service on Linux.
- Balance the order of code samples so that non-Windows stacks (Node.js, Python, Java) are presented before or alongside Windows/.NET examples.
- Explicitly mention any platform differences in how client certificates are handled in App Service on Linux vs. Windows.
- Provide guidance for validating client certificates using common Linux tools or scripting languages (e.g., Bash, OpenSSL, curl) in addition to .NET/Windows approaches.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell examples are provided alongside Azure CLI, but there are no Bash or Linux shell equivalents for PowerShell commands. Outbound IPv6 support is noted as available only for Windows apps, with no Linux parity. In command examples, PowerShell is presented as an alternative to Azure CLI, but no Linux-native scripting or command-line examples are given. The documentation references Windows-specific features and limitations before mentioning Linux, and Linux-specific guidance is minimal or missing.
Recommendations
- For every PowerShell example, provide an equivalent Bash/Linux shell example, especially for commands that retrieve app properties.
- Explicitly state Linux support or limitations in all relevant sections, not just in IPv6 outbound support.
- When listing command-line options, present Azure CLI (cross-platform) examples first, followed by PowerShell, and include Bash where appropriate.
- Clarify in all relevant sections whether features or commands apply to both Windows and Linux App Service plans.
- Add troubleshooting and verification steps for Linux environments, such as using dig or host commands in addition to nslookup.
- Where outbound IPv6 is not supported for Linux, provide a roadmap or workaround, or link to relevant tracking issues.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell script for automation but omitting equivalent Bash or Linux shell examples. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no Bash/Linux script or example. There are no explicit Linux-specific instructions or screenshots, and the general workflow assumes portal-based (GUI) steps, which are platform-agnostic but often more familiar to Windows users. The only mention of Linux is a reference to a separate Node.js guide, not present in this document.
Recommendations
- Add Bash or Linux shell script examples for automating certificate binding, alongside PowerShell.
- Provide explicit Azure CLI command examples inline, not just as links.
- Include Linux-specific notes or screenshots where relevant, such as uploading certificates from Linux systems.
- Ensure parity in automation instructions by treating CLI and PowerShell equally, and avoid presenting PowerShell first or exclusively.
- Reference Linux and cross-platform tools or workflows where appropriate, not just Windows-centric ones.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-configure-tls-mutual-auth.md
...p-service/app-service-web-configure-tls-mutual-auth.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing ASP.NET (Core and Web Forms) code samples, which are primarily Windows-centric technologies, and by referencing Windows-specific request properties (e.g., HttpRequest.ClientCertificate). There are no explicit Linux command-line examples (such as Bash or shell commands), and the documentation does not discuss Linux-specific certificate handling or tools. The Azure CLI and Bicep/ARM sections are cross-platform, but the application code samples and explanations are heavily skewed toward Windows development patterns and frameworks.
Recommendations
- Add Linux-specific examples, such as using Bash or OpenSSL commands to test mutual TLS connections or to inspect client certificates.
- Include code samples for popular Linux web frameworks (e.g., Nginx, Apache, or Kestrel on Linux) showing how to access and validate client certificates.
- Clarify that the .NET code samples are cross-platform when run on .NET Core, and provide guidance for running them on Linux-based App Service plans.
- Mention and provide examples of Linux-native tools (such as curl with client certificates, or OpenSSL s_client) for testing mutual TLS.
- Balance the order of examples so that Linux and cross-platform approaches are presented alongside or before Windows-centric ones.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md
...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its automation section by providing a PowerShell script example but omitting a corresponding Linux shell (Bash) example. The scripting section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, while the Azure CLI is linked. There are no explicit Linux/Bash command examples, and the PowerShell example is given more prominence. The rest of the documentation is largely platform-neutral, but the automation section prioritizes Windows tooling.
Recommendations
- Provide a Bash shell script example for Linux users alongside the PowerShell example in the automation section.
- Show both Azure CLI and PowerShell scripts inline, or at least give them equal prominence.
- Explicitly mention that the Azure CLI commands work cross-platform (Windows, Linux, macOS) to encourage Linux usage.
- Where scripting is referenced, ensure parity by including both Windows and Linux command-line approaches.
- Consider adding a note or section for Linux users, especially in automation contexts, to improve inclusivity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing Azure PowerShell examples alongside Azure CLI, but does not offer equivalent Linux shell or Bash scripting examples. PowerShell commands are presented as a primary method for retrieving outbound IP addresses, and outbound IPv6 support is noted as available only for Windows apps, with no Linux parity. There is also a lack of explicit Linux-focused guidance or troubleshooting, and the documentation does not mention Linux-specific tools or patterns.
Recommendations
- Provide Bash or Linux shell script examples for all command-line operations, especially where PowerShell is shown.
- Clarify the availability and limitations of features (such as outbound IPv6) for both Windows and Linux App Service apps, and provide guidance or workarounds for Linux users.
- When listing command-line examples, present Azure CLI (cross-platform) examples before PowerShell, and clearly indicate which platforms each example is intended for.
- Include troubleshooting steps or notes relevant to Linux users, such as differences in DNS tools or network stack behavior.
- Where PowerShell is referenced, offer equivalent Linux-native alternatives (e.g., Bash, curl, dig, jq) for common tasks.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for retrieving outbound IP addresses, but PowerShell examples are always included alongside CLI, and there are no Linux- or bash-specific examples for tasks that could be performed with native Linux tools (e.g., using curl or dig for DNS/IP queries). The documentation refers to 'local terminal' for nslookup but does not clarify cross-platform alternatives or mention Linux-specific tools. Outbound IPv6 support is noted as being available only for Windows apps, but this is a platform limitation, not a documentation bias.
Recommendations
- For all command-line examples, ensure that bash/Linux-native equivalents are provided where possible (e.g., using dig or host for DNS lookups, or curl for HTTP requests).
- When listing multiple command-line options, present Azure CLI (cross-platform) examples before PowerShell, or clearly indicate that both are supported on all platforms.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and clarify any platform-specific differences.
- Where PowerShell is shown, consider also showing bash or shell script equivalents for common administrative tasks.
- In sections referencing 'local terminal', clarify that commands work on both Windows and Linux/macOS, and suggest alternative tools if needed.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows/Powershell tools and patterns before Linux equivalents, providing more detail for Windows scenarios, and omitting Linux-specific automation examples (e.g., no Bash scripting or Linux CLI nuances). While Azure CLI is cross-platform, the PowerShell section is highlighted and no Linux shell scripting is shown. The documentation also refers to Windows-specific behaviors and features before Linux ones.
Recommendations
- Provide Linux/Bash shell scripting examples alongside or before PowerShell examples in the automation section.
- Explicitly mention that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any Linux-specific flags or considerations if applicable.
- Balance the order of presentation: when listing availability or features, alternate or combine Windows and Linux information rather than listing Windows first.
- Include troubleshooting or configuration steps that are specific to Linux environments, such as permissions or environment variables, if relevant.
- Where screenshots or portal instructions are given, clarify any differences in experience for Linux-hosted apps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-sidecar-multi-container-apps.md
...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by requiring PowerShell for the migration script, providing only PowerShell commands for key steps (such as decoding base64), and referencing a .ps1 script without any Linux shell or Bash alternatives. There are no Linux or Bash equivalents for the script-based migration, and PowerShell is listed as a prerequisite. This may hinder Linux/macOS users, who are likely to use Bash or other Unix shells.
Recommendations
- Provide Bash or shell script equivalents for all PowerShell commands, especially for decoding base64 and running migration scripts.
- Offer a cross-platform migration script (e.g., a Bash script or a Docker container) or document how to run the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
- List prerequisites in a cross-platform way, e.g., 'PowerShell (Windows) or Bash (Linux/macOS)'.
- Where possible, use Azure CLI and Docker commands, which are cross-platform, and avoid steps that require Windows-only tools.
- Add explicit Linux/macOS instructions or notes for each step that currently only shows a Windows/PowerShell approach.