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 1151-1175 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-identity.md
...main/articles/app-service/overview-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive examples using Azure PowerShell and references to PowerShell scripting, which is primarily a Windows-centric tool. In several cases, PowerShell is presented as a primary or parallel option to Azure CLI, and some code blocks are labeled as 'azurepowershell-interactive' even under CLI sections. There is no explicit mention of Linux shell scripting or Linux-specific command-line environments, and no examples are provided for Bash or other common Linux shells. The documentation assumes familiarity with PowerShell and does not offer parity for Linux users in scripting or tooling guidance.
Recommendations
- Add explicit Bash or Linux shell script examples alongside PowerShell for all relevant operations, especially for token retrieval and identity management.
- Clarify in each section whether the Azure CLI and PowerShell examples are cross-platform, and provide notes or links for Linux/macOS users where appropriate.
- Avoid labeling CLI examples as 'azurepowershell-interactive' when they are meant for Azure CLI, to reduce confusion.
- Where PowerShell is not supported (e.g., user-assigned identity for App Service), explicitly mention alternative Linux-compatible approaches.
- Include a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
- Ensure that all code samples and instructions are tested and confirmed to work on both Windows and Linux platforms.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-basic-auth-disable.md
...n/articles/app-service/configure-basic-auth-disable.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools and deployment patterns (such as Web Deploy/MSDeploy and Visual Studio) without providing Linux-specific equivalents or examples. The discussion of deployment agents and troubleshooting focuses on Windows agents, and there is no mention of Linux command-line tools (e.g., sftp, curl) or Linux-specific deployment workflows. Additionally, the documentation does not provide parity in examples or troubleshooting for Linux users.
Recommendations
- Include Linux-specific deployment examples, such as using sftp or Linux CLI tools for FTP/S deployments.
- When referencing Visual Studio or Web Deploy, also mention cross-platform alternatives (e.g., VS Code, Azure CLI, Git) and clarify their support on Linux.
- In troubleshooting and agent discussions, provide guidance for both Windows and Linux agents, including any differences in authentication or fallback behaviors.
- Add explicit notes or sections for Linux users where workflows or commands differ, ensuring Linux parity in all deployment and configuration scenarios.
- When listing deployment methods or tools, avoid always listing Windows tools first; alternate or group by platform where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-apple.md
...app-service/configure-authentication-provider-apple.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a bias towards Windows environments by providing only a C# example using the Microsoft.IdentityModel.Tokens NuGet package (which is Windows/.NET-centric), and referencing CngKey and ECDsaCng, which are Windows-specific cryptography APIs. There are no examples or guidance for Linux users or for cross-platform tools/libraries (such as OpenSSL, Python, or Node.js). There is also no mention of how to generate the JWT client secret on Linux or macOS, nor are any cross-platform command-line examples provided.
Recommendations
- Add examples for generating the client secret JWT using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
- Explicitly mention and provide code snippets for Linux and macOS users, including how to handle the .p8 key file and sign JWTs.
- Avoid using Windows-specific APIs (like CngKey, ECDsaCng) in the only example, or at least provide alternatives for other platforms.
- List cross-platform libraries and tools before or alongside Windows/.NET options.
- Include a table or section comparing approaches for Windows, Linux, and macOS environments.
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-first bias by presenting Windows SKU availability before Linux, providing Azure PowerShell automation examples (which are Windows-centric), and referencing Windows-specific behaviors and limitations. There are no Linux shell scripting examples (e.g., Bash), and PowerShell is highlighted as a primary automation tool, which may not be familiar or available on all Linux environments. The documentation also refers to the Azure portal UI without clarifying any platform differences, and does not provide parity in Linux-native automation or troubleshooting approaches.
Recommendations
- Present Linux and Windows options in parallel, or alternate which comes first to avoid implicit prioritization.
- Add Bash shell scripting examples for automating tasks, alongside PowerShell, to support Linux users.
- Clarify any platform-specific differences in the Azure portal UI, if applicable.
- Explicitly mention cross-platform compatibility for CLI and scripting tools.
- Where PowerShell is referenced, note that it is available cross-platform, but provide native Bash alternatives for Linux users.
- Ensure troubleshooting and error-handling guidance is not Windows-specific and includes Linux scenarios.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples for exporting App Service certificates using Azure CLI and Azure PowerShell, but does not include any Linux- or Unix-specific examples or guidance beyond the Azure CLI. The PowerShell example is given equal prominence to the CLI, and the FAQ specifically references PowerShell for troubleshooting. There are no examples or notes about Linux certificate management tools or workflows, nor is there any mention of platform-specific considerations for Linux users.
Recommendations
- Add explicit Linux/Unix shell examples for certificate export and management, such as using OpenSSL to inspect or convert the downloaded .pfx file.
- Clarify that Azure CLI commands are cross-platform and provide any necessary notes for Linux users (e.g., file permissions, dependencies).
- Include troubleshooting steps or FAQs relevant to Linux environments, not just PowerShell.
- Where PowerShell is referenced, consider also referencing Bash or other common Linux shells to ensure parity.
- If any UI screenshots or instructions are OS-specific, clarify their applicability or provide Linux-relevant alternatives.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-gateway-required-vnet-integration.md
...service/configure-gateway-required-vnet-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows. Gateway-required virtual network integration is explicitly stated to only work for Windows plans, with Linux apps not supported. All troubleshooting and connectivity examples use Windows-specific tools and commands (e.g., PowerShell's Test-NetConnection, netstat -aon), with no mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting steps, and the documentation does not acknowledge how Linux users might perform similar tasks.
Recommendations
- Clearly state at the beginning that gateway-required virtual network integration is not supported for Linux apps, and provide a prominent pointer to regional virtual network integration for Linux users.
- Where Windows-only features or tools are discussed, provide equivalent Linux guidance or explicitly state that the feature is not available for Linux.
- In troubleshooting sections, include Linux command equivalents for network testing (e.g., use 'nc', 'ss', or 'netcat' for TCP connectivity, 'lsof' or 'ss' for port listening, and 'dig' or 'host' for DNS resolution).
- When referencing environment variables or the Kudu console, mention how Linux users can access similar information (e.g., via SSH or the Azure portal).
- Add a summary table or section comparing feature support and troubleshooting steps for Windows vs. Linux, to help users quickly understand platform differences.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-vnet-integration-enable.md
...icles/app-service/configure-vnet-integration-enable.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for configuring virtual network integration, but the PowerShell section is significantly more detailed, with step-by-step parameter preparation and multiple command blocks. PowerShell is a Windows-centric tool, and its prominence, along with the lack of Bash or Linux shell examples, indicates a Windows-first and PowerShell-heavy bias. There are no Linux-specific instructions or examples, and the documentation assumes familiarity with PowerShell patterns and tools.
Recommendations
- Provide equivalent Bash or shell script examples for Linux users, especially for multi-step operations currently only shown in PowerShell.
- Ensure that CLI examples are as detailed as PowerShell ones, including parameter preparation, validation, and advanced scenarios (such as cross-subscription integration).
- Explicitly mention that Azure CLI is cross-platform and can be used on Windows, macOS, and Linux, and avoid assuming PowerShell as the default scripting environment.
- Where possible, structure the documentation so that cross-platform (CLI/Bash) instructions appear before or alongside PowerShell instructions, not after.
- Add notes or links to Linux-specific guidance or troubleshooting for common issues encountered on non-Windows platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-best-practices.md
...lob/main/articles/app-service/deploy-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias, particularly in the deployment mechanisms section. Kudu is described as running as a separate process in Windows App Service and only as a 'second container' in Linux, with more detail and emphasis on the Windows implementation. FTP and WebDeploy are mentioned as deployment mechanisms, but WebDeploy is a Windows-specific tool, and no Linux equivalents (such as rsync or SCP) are discussed. There are no explicit Linux command-line examples or references to Linux-native deployment tools. While the GitHub Actions example uses Ubuntu runners and Docker (which are cross-platform), the overall framing and tool mentions prioritize Windows or Windows-centric tools and patterns.
Recommendations
- Provide explicit Linux-native deployment examples, such as using SCP, rsync, or SFTP for file transfers.
- When mentioning deployment mechanisms, clarify which are cross-platform and which are Windows-only, and suggest Linux alternatives where appropriate.
- Balance the discussion of Kudu by giving equal detail to its operation on Linux (as a container) and Windows (as a process), and clarify any differences in usage or troubleshooting.
- Include references to Linux command-line tools and workflows (e.g., using Azure CLI on Linux, or integrating with Linux-based CI/CD tools).
- If mentioning WebDeploy, also mention that it is Windows-specific and suggest alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-hybrid-connections.md
...articles/app-service/app-service-hybrid-connections.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are often presented first or exclusively, with more detailed guidance and screenshots for Windows users. PowerShell commands are used for connectivity testing, and GUI-based workflows are only available on Windows. Linux support is present but less emphasized, with some features (like the GUI) unavailable and less detailed troubleshooting guidance for Linux environments.
Recommendations
- Present Windows and Linux instructions in parallel or in a more balanced way, rather than defaulting to Windows-first ordering.
- Where PowerShell commands are given (e.g., Test-NetConnection), provide equivalent Linux commands (such as 'nc', 'telnet', or 'curl') for connectivity testing.
- Expand Linux troubleshooting guidance, including common commands and diagnostic steps relevant to Linux environments.
- Clarify feature parity and limitations up front, and provide alternative Linux workflows where GUI tools are not available.
- Include more Linux-specific screenshots and examples, especially for CLI workflows.
- Where GUI-only features exist on Windows, suggest or document equivalent CLI or script-based approaches for Linux users.
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 detailed C# examples before other languages. The only explicit mention of platform-specific access to the client certificate is for ASP.NET, with no equivalent Linux/Unix-specific guidance. There are no examples or instructions for Linux command-line tools (such as Bash, OpenSSL, or curl), nor is there any mention of Linux-specific configuration or troubleshooting. The use of Azure CLI and Bicep is cross-platform, but the overall narrative and sample ordering favor Windows and Microsoft technologies.
Recommendations
- Add Linux/Unix-specific instructions and examples, such as how to use OpenSSL or curl to test mutual TLS authentication.
- Include guidance for accessing and validating client certificates in popular Linux web servers (e.g., Nginx, Apache) when running on App Service for Linux.
- Provide Bash shell examples alongside Azure CLI and Bicep, demonstrating how to interact with the API or test mutual TLS.
- Reorder language samples to alternate or balance Windows and Linux-first frameworks (e.g., show Node.js, Python, or Java before or alongside C#).
- Explicitly mention that the provided code samples work on both Windows and Linux, or note any platform-specific considerations.
- Add troubleshooting steps or notes for Linux environments, such as permissions, certificate store locations, or common errors.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-customize-sign-in-out.md
...vice/configure-authentication-customize-sign-in-out.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides a server-level authorization example exclusively for Windows apps using IIS and web.config, with no equivalent example or guidance for Linux-based App Service apps. The section is labeled 'Windows apps only', and Linux users are told that 'Linux apps don't use IIS and can't be configured through web.config', but no alternative is offered. Additionally, the use of Kudu (which is available on both platforms) is described in the context of editing web.config, reinforcing a Windows-centric approach. There are no PowerShell-specific examples, but the overall pattern prioritizes Windows tooling and omits Linux parity.
Recommendations
- Add equivalent Linux guidance: Provide an example of how to implement server-level authorization for Linux-based App Service apps, such as using middleware in common frameworks (e.g., Node.js, Python, .NET Core) or via .htaccess for PHP.
- Clarify cross-platform tooling: When mentioning tools like Kudu, clarify their availability and usage on both Windows and Linux App Service plans.
- Balance examples: Where platform-specific configuration is discussed, ensure both Windows and Linux approaches are presented side by side, or clearly direct Linux users to appropriate resources.
- Explicitly state limitations: If certain features are not available on Linux, explain why and suggest best practices or workarounds for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-php.md
...ob/main/articles/app-service/configure-language-php.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux by using platform pivots for most configuration tasks. However, there are notable signs of Windows bias: Windows instructions and tools (such as KuduScript and references to Windows paths) are often presented first, and some deployment automation examples (Composer, Bower, Gulp, Grunt) are only detailed for Windows, with no equivalent Linux scripting guidance. Windows-specific tools and patterns (e.g., Kudu, .dll extensions, Windows directory structures) are referenced more explicitly, while Linux alternatives are less detailed or missing.
Recommendations
- Provide Linux-specific examples for Composer, Bower, Gulp, and Grunt deployment automation, similar to the detailed Windows/KuduScript instructions.
- Ensure that Linux instructions are presented with equal prominence and detail as Windows, especially for common developer workflows.
- Avoid referencing Windows tools (like KuduScript) without mentioning or linking to Linux equivalents or alternatives.
- When showing directory paths or file extensions, always provide both Windows and Linux formats side by side.
- Consider alternating the order of Windows and Linux pivots or providing a neutral introduction before platform-specific sections.
- Where a tool or workflow is only available on Windows, explicitly state this and suggest Linux alternatives if possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-hybrid-connections.md
...articles/app-service/app-service-hybrid-connections.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows instructions, tools, and troubleshooting steps are often presented first or exclusively, with more detail and GUI options than for Linux. PowerShell commands are used for connectivity testing, and some troubleshooting steps and GUI tools are only available for Windows. Linux instructions are present but sometimes less detailed, and Linux users are directed to CLI-only workflows, with some missing parity in troubleshooting examples.
Recommendations
- Present Linux and Windows instructions in parallel or in a more balanced order, rather than always listing Windows first.
- Provide Linux equivalents for all troubleshooting steps, such as using 'nc' (netcat) or 'curl' for connectivity tests instead of only PowerShell's 'Test-NetConnection'.
- Expand Linux installation and usage instructions to match the detail and clarity of Windows sections, including more screenshots or terminal outputs where appropriate.
- Where GUI tools are only available on Windows, explicitly state this early and offer alternative Linux workflows or tools, possibly with example scripts.
- Ensure all command-line examples (e.g., for testing connectivity, DNS resolution) are provided for both Windows (PowerShell/CMD) and Linux (bash), ideally side-by-side.
- In troubleshooting sections, include Linux-native commands (e.g., 'nslookup', 'dig', 'nc', 'telnet') alongside Windows commands.
- Review the order of presentation so that Linux users do not feel like an afterthought; consider alternating which OS is presented first in each section.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-asp-net-migration.md
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias by focusing exclusively on migration scenarios and tools for ASP.NET web apps running on Windows/IIS servers. All migration tools and examples are tailored for Windows environments, with repeated references to IIS, PowerShell scripts, and Windows-specific migration assistants. There is no mention of Linux-based .NET hosting environments, nor are there any Linux migration tools, examples, or guidance provided.
Recommendations
- Include migration scenarios and tools for .NET apps hosted on Linux servers (e.g., Apache, Nginx, Kestrel).
- Provide Linux-specific migration guidance and examples, such as using Bash scripts or Linux-native tools.
- Mention and link to any available cross-platform or Linux-compatible migration assistants or scripts.
- Balance the documentation by presenting both Windows and Linux migration paths, or clarify if only Windows is supported and provide alternatives for Linux users.
- Add explicit notes about the current lack of Linux support (if applicable) and direct users to relevant resources for Linux-based .NET app migration.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-apple.md
...app-service/configure-authentication-provider-apple.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation provides a code example for generating the Apple client secret JWT using C# and the Microsoft.IdentityModel.Tokens NuGet package, which is primarily a Windows/.NET ecosystem tool. There are no equivalent examples or guidance for Linux users (e.g., using OpenSSL, Python, or Node.js). The documentation also references application settings and configuration in a way that assumes familiarity with Azure App Service patterns, which are more commonly managed via Windows-centric tooling. No Linux command-line or cross-platform code samples are provided.
Recommendations
- Add examples for generating the client secret JWT using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
- Explicitly mention that the C# example is one of several possible approaches, and provide links or code snippets for Linux/macOS users.
- Include command-line examples for managing application settings using Azure CLI (which is cross-platform), not just through the Azure portal.
- Review the documentation to ensure that any references to tooling or libraries are balanced with Linux-friendly or cross-platform alternatives.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-intelligent-apps-dotnet-to-azure-sql.md
...service/deploy-intelligent-apps-dotnet-to-azure-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific UI patterns (e.g., 'Right click', folder navigation), and by omitting any explicit Linux or cross-platform command-line instructions for common developer tasks (such as file creation, package installation, or database access). Tools like Azure Data Studio and SQL query editors are mentioned generically, but no Linux-specific alternatives or CLI-based workflows are provided. There are no PowerShell-specific commands, but the overall workflow assumes a GUI and Windows-centric development environment.
Recommendations
- Provide equivalent Linux/macOS instructions for tasks such as creating files (e.g., using 'touch' or 'nano' in the terminal) and installing packages (e.g., using 'dotnet add package' CLI).
- Include command-line examples for database access and management (e.g., using Azure CLI, sqlcmd, or Data Studio on Linux).
- Avoid UI instructions that are Windows-specific (such as 'Right click') or supplement them with cross-platform alternatives.
- Explicitly mention that all steps can be performed on Linux and macOS, and provide any necessary prerequisites or caveats.
- Where GUI tools are referenced, note their cross-platform availability or suggest alternatives for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate.md
...main/articles/app-service/configure-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While it provides some cross-platform guidance (e.g., OpenSSL commands for certificate export), it references Windows-specific tools (IIS, Certreq.exe) without equivalent Linux alternatives, lists Azure PowerShell examples alongside Azure CLI but does not provide Bash or Linux-native scripting examples, and refers to Windows-specific scenarios in FAQs. Linux tools and workflows are either missing or mentioned after Windows options.
Recommendations
- When referencing Windows tools like IIS or Certreq.exe for certificate export, also provide equivalent Linux commands or tools (e.g., OpenSSL, certbot, or native Linux certificate management instructions).
- Include Linux/Bash scripting examples for automation tasks, not just Azure CLI and PowerShell.
- In FAQs and scenario explanations, clarify Linux support and provide Linux-specific guidance where features differ (e.g., outbound client certificate support in Linux containers).
- Ensure that cross-platform tools (like OpenSSL) are presented as primary options, and avoid implying Windows tools are the default or preferred method.
- Where PowerShell is used, provide Bash or shell script equivalents for Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-azure-pipelines.md
...ob/main/articles/app-service/deploy-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: deployment examples and templates are primarily focused on ASP.NET (a Windows-centric technology), and the only explicit agent pool example for Web Deploy uses 'windows-latest'. The FAQ and troubleshooting sections reinforce that Web Deploy is only supported on Windows agents, without offering Linux alternatives or workarounds. There are no PowerShell scripts, but the overall pattern and tool selection (Web Deploy, IIS references) are Windows-centric. Linux deployment scenarios are not given equal prominence or detailed examples.
Recommendations
- Provide parallel examples for Linux-based deployments, especially for non-.NET stacks (Node.js, Python, Java).
- Explicitly mention and demonstrate how to use Linux agents for all supported deployment types, including any limitations.
- Where a feature is Windows-only (e.g., Web Deploy), offer alternative Linux-compatible deployment methods and document them with examples.
- Balance the initial examples and templates to include at least one Linux-first scenario (e.g., Node.js on Linux App Service).
- Clarify in the prerequisites and FAQ which features are cross-platform and which are Windows-specific, and link to Linux guidance 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 in its automation section by providing a PowerShell script example but omitting equivalent Linux/bash scripting examples. The automation section lists Azure CLI and PowerShell, but only the PowerShell script is shown inline, while the Azure CLI is merely linked. There are no explicit Linux or cross-platform shell examples, and PowerShell is highlighted first and more prominently. Additionally, there are no references to Linux-specific tools or workflows elsewhere in the document.
Recommendations
- Provide inline Azure CLI/bash examples alongside PowerShell scripts in the automation section, ensuring both are equally visible.
- Explicitly mention that the Azure CLI commands can be run on Linux, macOS, and Windows, and provide sample bash scripts for Linux users.
- Review the ordering of automation examples to avoid always listing PowerShell first; consider alternating or listing CLI/bash first where appropriate.
- Add references or links to Linux-specific workflows or troubleshooting where relevant, such as certificate management or file paths.
- Ensure screenshots and walkthroughs do not assume a Windows environment unless necessary, and clarify when steps are platform-agnostic.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide.md
...rvice-web-nodejs-best-practices-and-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows using iisnode. All configuration examples, troubleshooting steps, and tool references are Windows-centric (e.g., node.exe, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell, IIS, and DLLs). There are no Linux or cross-platform equivalents provided, and Linux troubleshooting or deployment patterns are not mentioned.
Recommendations
- Add equivalent sections or links for Node.js on Azure App Service for Linux, including configuration and troubleshooting steps.
- Provide Linux-based examples (e.g., using PM2, systemd, or NGINX instead of IIS/iisnode) alongside or before Windows examples.
- Include Linux-specific file paths, error log locations, and diagnostic tools (such as journalctl, systemctl, or Linux shell commands).
- Reference cross-platform Node.js debugging and profiling tools, and clarify which steps are Windows-only.
- Clearly label Windows-specific content and provide navigation or pivots to Linux content where available.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell instructions and tooling first, referencing Visual Studio (a Windows-centric IDE) for initial setup, and relying on PowerShell modules for key steps. While an Azure CLI example is provided, the PowerShell approach is given primary placement, and there is no explicit mention of Linux or cross-platform development environments.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Include explicit notes or sections for Linux/macOS users, such as how to perform steps in Bash or with other common Linux tools.
- Avoid assuming Visual Studio as the default development environment; mention alternatives like VS Code or command-line deployment.
- Where PowerShell is used, clarify if it is supported on Linux/macOS (PowerShell Core), and provide equivalent Bash or shell commands if possible.
- Add a brief section or callout confirming that all steps are supported on Linux and macOS, and link to any relevant platform-specific guidance.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-encrypt-at-rest-using-cmk.md
...les/app-service/configure-encrypt-at-rest-using-cmk.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily by recommending Azure Storage Explorer (a GUI tool with a Windows-first experience) for uploading files and generating SAS tokens, and by referencing instructions with a '?tabs=windows' parameter. There are no explicit Linux or cross-platform CLI alternatives provided for these steps, and no mention of Linux-native tools or workflows for managing storage or SAS tokens. All command-line examples use Azure CLI, which is cross-platform, but the critical file upload and SAS generation steps are described only via a Windows-centric GUI tool.
Recommendations
- Provide equivalent instructions for uploading files and generating SAS tokens using Azure CLI or AzCopy, both of which are cross-platform.
- Avoid linking to documentation with '?tabs=windows' unless also providing Linux/macOS tabs or alternatives.
- Mention that Azure Storage Explorer is available on Linux and macOS, or clarify its cross-platform support if referenced.
- Include explicit Linux/macOS command-line examples for all steps currently described only via GUI or Windows-centric tools.
- Consider reordering or parallelizing instructions so that CLI/cross-platform approaches are presented before or alongside Windows GUI methods.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-vnet-integration-enable.md
...icles/app-service/configure-vnet-integration-enable.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides detailed instructions and code samples for Azure PowerShell, which is primarily a Windows-centric tool, alongside Azure CLI. The PowerShell section is more elaborate, with step-by-step parameter preparation and resource manipulation, while the CLI section is brief. There are no Linux shell or Bash-specific examples, and the PowerShell approach is presented after the CLI but with more depth and context, indicating a bias toward Windows tooling and patterns.
Recommendations
- Add equivalent Bash or Linux shell examples for all CLI commands, including parameter preparation and validation steps.
- Ensure that CLI and PowerShell sections are equally detailed, or provide parity in explanations and troubleshooting.
- Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- If possible, provide examples using native Linux tools (such as curl or jq) for related tasks, or clarify when PowerShell is not required.
- Consider reordering sections so that cross-platform tools (CLI) are featured before or with equal prominence to Windows-specific tools (PowerShell).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/overview-certificates.md
...icles/app-service/environment/overview-certificates.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 only PowerShell examples for certificate generation and management, referencing Windows-specific certificate stores (Cert:\LocalMachine\Root), and explicitly stating that private client certificates are only supported from custom code in Windows code apps. There are no equivalent Linux or cross-platform instructions or examples, and Linux scenarios are not addressed.
Recommendations
- Provide equivalent Linux/bash examples for certificate generation (e.g., using openssl) and management.
- Clarify the support matrix for private client certificates on Linux and other platforms, and offer workarounds or alternatives if possible.
- Include instructions for verifying certificate installation on Linux (e.g., using the bash shell in Kudu or relevant Linux commands).
- Avoid referencing only Windows certificate stores; mention Linux trust store locations and how to interact with them.
- Structure examples so that both Windows and Linux users can follow along, ideally presenting both side-by-side or in a platform-agnostic way where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/getting-started.md
...docs/blob/main/articles/app-service/getting-started.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows some Windows bias, especially in the .NET and Python sections. Windows tools (Visual Studio, Azure PowerShell) are listed before cross-platform or Linux-native tools, and in some cases, Linux-specific examples are less prominent or missing. The .NET stack emphasizes Windows-centric development environments and tools, while Linux parity is stronger in Java, Node.js, and PHP sections.
Recommendations
- Ensure that for each stack, Linux-native tools (e.g., Azure CLI, VS Code, Bash) are listed before or alongside Windows tools (e.g., Visual Studio, PowerShell).
- Provide explicit Linux examples and tabs for all quickstarts and tutorials, especially for .NET and Python stacks.
- Avoid listing Windows-only tools (like Visual Studio or PowerShell) as the default or first option; instead, present cross-platform tools first.
- Where possible, add parity in deployment and configuration instructions for both Windows and Linux environments.
- Review the use of 'Windows' in tab names and links to ensure Linux options are equally visible and accessible.