Scan Details - Linux-first Docs for Azure

Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/access-tokens.md ...ob/main/articles/active-directory-b2c/access-tokens.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation page demonstrates Windows bias by exclusively mentioning Microsoft PowerShell as an example HTTP client for testing the POST request, without referencing cross-platform or Linux-native tools such as curl or wget. No Linux-specific or cross-platform command-line examples are provided, and the only tool recommendation is Windows-centric. This may hinder Linux developers or those using non-Windows environments from easily following the instructions.

Recommendations

Include examples using curl and/or wget for making HTTP requests, alongside or before PowerShell.
Explicitly mention that any HTTP client can be used, and provide links to documentation for popular Linux and cross-platform tools.
Add sample command-line requests for Linux/macOS environments.
Ensure tool recommendations are platform-neutral or presented in parallel (e.g., 'You can use PowerShell (Windows), curl (Linux/macOS), or any HTTP client...').

Create Pull Request

Active Directory B2C https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory-b2c/force-password-reset.md .../articles/active-directory-b2c/force-password-reset.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first

Summary

The documentation page demonstrates a Windows bias by providing only PowerShell examples for command-line operations (such as updating password expiry duration), referencing Windows-centric tools (PowerShell cmdlets), and omitting equivalent instructions for Linux/macOS environments (such as using Azure CLI, Bash, or REST API via curl). The order of presentation also favors Windows tools, with no mention of cross-platform alternatives.

Recommendations

Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
Include REST API usage examples with curl or HTTPie for platform-neutral instructions.
Clearly indicate that PowerShell examples are for Windows and offer alternatives for other operating systems.
Reorder sections or add notes to ensure cross-platform tools are presented alongside or before Windows-specific tools.
Reference installation and usage of Microsoft Graph PowerShell module on non-Windows platforms, if supported.

Create Pull Request

API Management https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/quickstart-terraform.md ...b/main/articles/api-management/quickstart-terraform.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but presents Azure CLI (cross-platform) first, followed by Azure PowerShell (Windows-centric). There are no explicit Linux shell examples (e.g., bash scripts), and the PowerShell section uses Windows-style variable assignment. The prerequisites mention both Azure CLI and PowerShell, but do not clarify platform parity or recommend cross-platform tools over Windows-specific ones.

Recommendations

Add explicit bash/Linux shell examples where applicable, especially for variable assignment and command usage.
Clarify in prerequisites that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
Consider adding a 'Bash' or 'Linux shell' tab alongside Azure CLI and PowerShell for command-line steps.
When referencing tools, mention cross-platform options first and provide clear guidance for users on different operating systems.
Review code snippets to ensure they are not using Windows-specific syntax unless necessary, and provide equivalent Linux/macOS alternatives.

Create Pull Request

App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-java-data-sources.md ...es/app-service/configure-language-java-data-sources.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides both Windows and Linux instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, the Windows section is notably more detailed, with extensive PowerShell scripting and Windows-specific patterns (e.g., copying Tomcat to a local directory, using %LOCAL_EXPANDED%, and leveraging PowerShell for XSLT transforms). The Linux instructions are present but less detailed, often referencing external scripts or general approaches without as much step-by-step guidance. Windows tools and patterns (e.g., PowerShell, Windows environment variables) are emphasized, and the Windows section appears after the Linux section but is much more comprehensive. There are also cases where Linux instructions reference uploading scripts but do not provide as much explicit scripting detail as for Windows.

Recommendations

Provide equally detailed, step-by-step Linux examples for tasks that are covered in detail for Windows, such as automating Tomcat configuration changes using shell scripts (e.g., bash) instead of PowerShell.
Where PowerShell scripts are given for Windows, provide equivalent bash or shell scripts for Linux, including examples for copying Tomcat, performing XSLT transforms, and managing environment variables.
Avoid using Windows-specific environment variables (e.g., %HOME%, %LOCAL_EXPANDED%) in general explanations; instead, provide Linux equivalents (e.g., $HOME, /home/site/wwwroot) side-by-side.
Ensure that Linux tools (e.g., bash, sh, sed, xsltproc) are mentioned and demonstrated with the same level of detail as Windows tools.
Consider reordering or parallelizing the instructions so that for each major step, both Windows and Linux approaches are presented together for easier comparison.
Add troubleshooting tips and common pitfalls for Linux users, similar to what is often included for Windows scenarios.

Create Pull Request

App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md ...main/articles/app-service/configure-language-nodejs.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation demonstrates a moderate Windows bias. Windows instructions and tools (such as IISNode and web.config) are often presented first or in more detail, with Linux equivalents sometimes relegated to later sections or less detailed explanations. There is a reference to using PowerShell for Application Insights instrumentation, but no equivalent Linux CLI or Bash example. Some troubleshooting and configuration steps are Windows-specific (e.g., web.config), while Linux guidance is less prominent or missing for certain scenarios.

Recommendations

Ensure parity in example order: Present Windows and Linux instructions side-by-side or alternate which platform is described first.
Provide Linux/Bash alternatives for all PowerShell or Windows-specific instructions, especially for Application Insights instrumentation.
Expand troubleshooting and configuration sections to include Linux-specific guidance and common issues (e.g., container startup, permissions, config files).
Where Windows tools (IISNode, web.config) are discussed, clearly highlight Linux equivalents (PM2, startup scripts, etc.) and provide matching detail.
Audit all examples to ensure both platforms are equally represented and that Linux users are not required to infer steps from Windows instructions.

Create Pull Request

App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-app-service-certificate.md ...s/app-service/configure-ssl-app-service-certificate.md

High Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation demonstrates a Windows bias by providing Azure PowerShell examples alongside Azure CLI, but does not mention or provide Linux-specific shell examples (e.g., Bash, OpenSSL, or Linux certificate management tools). The ordering of examples places PowerShell after CLI, but the FAQ specifically references PowerShell. There is no mention of Linux certificate management patterns or tools, and all screenshots and portal instructions are platform-agnostic but implicitly Windows-oriented (e.g., PowerShell, lack of Linux shell references).

Recommendations

Add explicit Linux/Bash examples for certificate export and management, such as using OpenSSL to handle .pfx files.
Include notes or sections describing how to perform certificate management tasks on Linux systems, including command-line tools commonly used on Linux.
Balance the FAQ and troubleshooting sections to reference both PowerShell and Linux/Bash workflows.
If screenshots are relevant, include examples from Linux environments (e.g., Azure Cloud Shell in Bash mode).
Clarify that Azure CLI commands work cross-platform and provide guidance for Linux users where workflows differ.

Create Pull Request

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 →

Reviewed by: LLM Analysis

Issues: 4 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation page exhibits Windows bias by providing a PowerShell script example for automating certificate binding, while not offering equivalent Linux shell (Bash) examples. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, with no Bash or cross-platform scripting examples. The documentation refers to uploading .pfx files (a Windows-centric certificate format) without mentioning Linux-friendly alternatives like .pem. There is also a lack of explicit Linux workflow guidance, and Windows tools/patterns are mentioned or implied first.

Recommendations

Add Bash or cross-platform shell script examples alongside PowerShell in the automation section.
Provide explicit Linux workflow guidance, including certificate formats commonly used on Linux (.pem, .crt) and how to convert them to .pfx if needed.
Ensure Azure CLI examples are shown inline, not just as links, and clarify that Azure CLI is cross-platform.
Mention Linux tools (e.g., OpenSSL) for certificate management and provide example commands.
Review the order of tool presentation to avoid always listing Windows/PowerShell first.

Create Pull Request

Scan Information

Problematic Pages