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 1026-1050 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-webjobs.md
...ocs/blob/main/articles/app-service/overview-webjobs.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 Windows-specific tools and workflows, such as Visual Studio deployment to Windows App Service, while lacking explicit Linux deployment examples or references to Linux-compatible tools. The mention of Visual Studio deployment is specifically tied to Windows App Service, and there are no examples or guidance for deploying or managing WebJobs on Linux-based App Service plans. Additionally, tools like Kudu are referenced without clarifying their availability or differences on Linux App Service.
Recommendations
- Add explicit examples and instructions for deploying WebJobs to Linux-based App Service plans, including supported languages, file types, and any limitations.
- Include Linux-friendly deployment workflows, such as using Azure CLI, FTP, or Git for Linux App Service, and clarify any differences from Windows.
- Mention cross-platform editors and tools (e.g., VS Code, Azure CLI) alongside or before Windows-specific tools like Visual Studio.
- Clarify the availability and differences of Kudu and App Service diagnostics on Linux App Service.
- Ensure that all references to deployment, monitoring, and troubleshooting cover both Windows and Linux scenarios equally.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based CLI examples for configuring per-app scaling, with no equivalent examples for Linux-native tools (such as Azure CLI/bash). The use of PowerShell cmdlets (e.g., New-AzAppServicePlan, Set-AzAppServicePlan, Get-AzWebApp) assumes a Windows or PowerShell Core environment. There are no bash, Azure CLI, or cross-platform scripting examples, and PowerShell is presented as the primary (and only) scripting interface. ARM template examples are platform-neutral, but all interactive/imperative examples are Windows-centric.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, using bash syntax to ensure Linux parity.
- Explicitly mention that PowerShell examples can be run cross-platform using PowerShell Core, but provide native bash/Azure CLI alternatives.
- Reorder sections or provide parallel examples so that Linux-native (Azure CLI/bash) and Windows-native (PowerShell) instructions are presented with equal prominence.
- Include a note or table summarizing all available automation interfaces (PowerShell, Azure CLI, ARM templates, REST API) and their platform compatibility.
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 displays a Windows bias by consistently presenting Windows-related information and tools first (e.g., Windows SKU availability before Linux, Azure PowerShell section before mentioning Linux scripting alternatives), providing PowerShell examples without corresponding Bash or Linux-native scripting examples, and referencing Windows-specific behaviors. Linux-specific instructions are present but less detailed, and there are no examples using Linux-native tools or shell scripting beyond Azure CLI.
Recommendations
- Present Linux and Windows options in parallel, or alternate which is shown first to avoid 'windows_first' ordering.
- Provide Bash or Linux shell script equivalents for all PowerShell automation examples.
- Explicitly mention Linux-native tools or workflows where relevant, not just Azure CLI.
- Clarify any differences in behavior or limitations between Windows and Linux App Service plans.
- Ensure screenshots and UI instructions are not Windows-centric (e.g., avoid only showing Windows portal views if Linux differs).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias primarily in the section addressing Azure Traffic Manager endpoints, where only a PowerShell script is provided for identifying non-Azure endpoints. There are no equivalent Bash, Azure CLI, or cross-platform scripting examples for Linux/macOS users. The instructions for running the script assume a Windows/PowerShell environment, and there is no mention of alternatives or parity for non-Windows platforms. Elsewhere, REST API and Azure CLI commands are referenced, which are cross-platform, but the exclusive use of PowerShell for a key scenario stands out as a bias.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying non-Azure Traffic Manager endpoints, ensuring Linux/macOS users can perform the same checks.
- Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, or provide guidance for cross-platform usage.
- When referencing scripts or tools, offer both Windows (PowerShell) and Linux/macOS (Bash/CLI) options, or clarify when a solution is platform-agnostic.
- Review documentation for other scenarios to ensure that all platform-specific tooling (e.g., scripts, commands) is accompanied by alternatives or clear cross-platform instructions.
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 explicit scripting example, referencing Azure CLI only as a link without an inline example, and omitting Linux-specific command-line or scripting workflows. The automation section lists PowerShell after Azure CLI but provides only a PowerShell code snippet, with no Bash or Linux-native example. There is also a lack of explicit Linux tooling or parity in the walkthrough steps.
Recommendations
- Add inline Azure CLI (Bash) examples alongside or before PowerShell examples in the 'Automate with scripts' section.
- Include Linux-native workflows or notes (e.g., using Bash, OpenSSL, or Linux file paths) when discussing certificate upload and management.
- Ensure that all scripting/code examples are provided for both Windows (PowerShell) and Linux (Bash/CLI), and that neither platform is prioritized in ordering.
- Reference Linux-specific documentation or troubleshooting where relevant, especially in sections about certificate file handling and environment-specific configuration.
- Review screenshots and UI instructions to ensure they are not Windows-centric, or provide Linux/CLI alternatives where possible.
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
Missing Linux Example
Summary
The documentation provides detailed PowerShell instructions first and in more depth, with a secondary Azure CLI example. There are no explicit Linux shell (bash) or cross-platform scripting examples, and the PowerShell example is more prominent. There is also an assumption of Visual Studio usage, which is Windows-centric.
Recommendations
- Provide bash or shell script examples for Linux users alongside PowerShell.
- List Azure CLI or bash examples before or alongside PowerShell to avoid Windows-first bias.
- Mention cross-platform development tools (such as VS Code) in addition to Visual Studio.
- Clarify that all steps can be performed on Linux/macOS as well as Windows, and note any OS-specific requirements.
- Ensure screenshots and UI instructions are not Windows-specific if the Azure Portal experience is the same across platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by presenting Windows-related tools and examples before their Linux equivalents, and by providing Azure PowerShell automation examples (which are more common on Windows) alongside Azure CLI. The Azure portal UI, which is more familiar to Windows users, is emphasized throughout. While Linux is mentioned (e.g., Linux container availability, Linux-specific CLI flag), there are no Linux shell-specific examples, and PowerShell is highlighted as a primary automation method.
Recommendations
- Provide Linux shell (bash) scripting examples alongside or before PowerShell examples for automation.
- Ensure parity in example order: present Linux and Windows options together, or alternate which comes first.
- Mention and link to Azure CLI usage from both Windows and Linux environments, clarifying cross-platform compatibility.
- Include screenshots or instructions for the Azure portal experience on Linux (if differences exist), or clarify that the portal is OS-agnostic.
- Where PowerShell is referenced, note that Azure CLI is fully supported on Linux and macOS, and provide bash/zsh equivalents where appropriate.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell-based), but it lists the Visual Studio/PowerShell method second. However, there is no explicit mention of Linux or cross-platform development environments beyond the .NET CLI, and no Linux-specific guidance or examples are provided. The focus on Visual Studio and PowerShell may implicitly favor Windows users, and the absence of Linux terminal or editor examples (such as VS Code or bash) further highlights this bias.
Recommendations
- Explicitly mention that the .NET Core CLI commands work on Linux, macOS, and Windows, and recommend it as the primary cross-platform method.
- Add Linux-specific instructions or examples, such as using bash or zsh terminals, and reference popular Linux editors (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
- Clarify that the Package Manager Console is only available in Visual Studio on Windows, and suggest alternatives for Linux users.
- Include a note or section on verifying package installation in Linux environments.
- Ensure parity in tooling and workflow coverage for both Windows and Linux users throughout the documentation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell examples for per-app scaling, referencing Azure PowerShell cmdlets exclusively, and omitting equivalent CLI or scripting instructions for Linux or cross-platform users. There are no Bash, Azure CLI, or Linux-native tool examples, and the PowerShell approach is presented first and as the primary method. This may hinder accessibility for users on Linux or macOS systems.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to create and configure per-app scaling using the CLI.
- Include Bash script examples where appropriate, especially for configuring app settings or deploying ARM templates.
- Clearly indicate that PowerShell is not required and that all operations can be performed cross-platform using the Azure CLI.
- Reorder sections or provide parallel examples so that Linux/cross-platform methods are not secondary to Windows/PowerShell.
- Mention and link to documentation on installing and using Azure CLI on Linux/macOS.
- If possible, provide screenshots or walkthroughs for the Azure Portal UI, which is platform-agnostic.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-webjobs.md
...ocs/blob/main/articles/app-service/overview-webjobs.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-specific tools and workflows (such as Visual Studio deployment to Windows App Service) and omitting explicit Linux deployment examples or Linux-specific considerations. Visual Studio and Windows App Service are mentioned before cross-platform or Linux-native tools, and there is no mention of Linux command-line deployment, file permissions, or troubleshooting on Linux-based App Service plans.
Recommendations
- Add explicit examples and instructions for deploying WebJobs to Linux-based App Service plans, including command-line (Azure CLI) and zip deployment workflows.
- Include references to cross-platform development environments (such as VS Code) and clarify any differences in deployment or monitoring on Linux vs. Windows App Service.
- Mention Linux-specific considerations, such as file permissions, supported runtimes, and troubleshooting steps for Linux environments.
- Reorder deployment options to present cross-platform and automation-first approaches (e.g., Azure CLI, GitHub Actions) before Windows-specific tools like Visual Studio.
- Ensure that all tooling and monitoring references (such as Kudu) are clarified for both Windows and Linux App Service plans, noting any differences.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In sections where both Windows and Linux are relevant (such as SKU availability), Windows examples and commands are presented before Linux equivalents. The automation section provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples, but PowerShell is given a dedicated section, reinforcing a Windows-centric approach. There are no Linux shell (bash) or scripting examples, and the documentation references Windows-specific patterns and tools (such as Azure PowerShell) without offering parity for Linux-native tools or workflows.
Recommendations
- Present Linux and Windows examples side by side, or alternate which is shown first to avoid implicit prioritization.
- Include bash or shell script examples for Linux users, especially in automation sections.
- Clarify that Azure CLI is cross-platform and can be used on both Windows and Linux, and consider providing examples of running CLI commands in both environments.
- If referencing Azure PowerShell, also mention and link to Linux-compatible alternatives or note PowerShell Core's cross-platform capabilities.
- Review screenshots and UI instructions to ensure they are not Windows-specific, or provide Linux/portal equivalents if differences exist.
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
Summary
The documentation shows mild Windows bias: Windows is mentioned first in availability, and Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being more cross-platform. There are no Linux shell or Bash script examples, and the portal UI instructions do not clarify OS-specific differences. However, Linux is mentioned in SKU availability and supported scenarios.
Recommendations
- Provide Bash shell script examples alongside PowerShell for automation, especially for Linux users.
- When listing availability or features, avoid listing Windows first unless there is a technical reason; consider parallel presentation or alternating order.
- Clarify any OS-specific differences in the Azure portal UI steps, if applicable.
- Explicitly state that Azure CLI commands work identically on Windows, Linux, and macOS, and recommend CLI for cross-platform automation.
- If mentioning PowerShell, clarify that PowerShell Core is available cross-platform, or provide Bash alternatives.
- Consider adding a table summarizing feature support for both Windows and Linux to improve parity and clarity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-webjobs.md
...ocs/blob/main/articles/app-service/overview-webjobs.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 Windows-specific tools and workflows (such as Visual Studio deployment to Windows App Service) and omitting explicit Linux deployment examples or Linux-native tooling. The mention of Visual Studio deploys 'directly with your ASP.NET app to Windows App Service' without referencing Linux App Service or cross-platform alternatives. There are no Linux command-line or scripting examples, and Kudu (which is more closely associated with Windows environments) is emphasized for diagnostics and logging.
Recommendations
- Add explicit examples and instructions for deploying WebJobs to Linux App Service plans, including using cross-platform tools like Azure CLI, VS Code, or GitHub Actions.
- Mention and demonstrate Linux-compatible deployment workflows (e.g., zip deploy via Azure CLI, FTP/SFTP, or GitHub Actions targeting Linux).
- Clarify which features or tools (such as Kudu) are available on both Windows and Linux App Service plans, and provide Linux-specific troubleshooting/logging guidance if different.
- Balance references to Visual Studio with equivalent cross-platform IDEs or editors (e.g., Visual Studio Code) and provide parity in documentation links.
- Ensure that all platform-specific instructions are clearly labeled, and provide alternatives for both Windows and Linux users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the section addressing Azure Traffic Manager endpoints. It exclusively recommends and documents a PowerShell script for identifying non-Azure endpoints, with no mention of Bash, Azure CLI, or cross-platform alternatives. The instructions for running the script are Windows/PowerShell-centric, and there is no guidance for Linux or macOS users. Elsewhere, while Azure CLI and REST API are referenced (which are cross-platform), the only explicit example of a script-based solution is PowerShell, and it is presented as the default and only option.
Recommendations
- Provide equivalent Bash or Azure CLI scripts for identifying non-Azure Traffic Manager endpoints, or at least reference cross-platform alternatives.
- Explicitly mention that the PowerShell script can be run on PowerShell Core (pwsh) on Linux/macOS, if applicable, and provide instructions for those environments.
- When referencing scripts or automation, offer both Windows (PowerShell) and Linux/macOS (Bash, Azure CLI) examples side by side.
- Review other areas for subtle Windows-first language or tool recommendations, and ensure Linux parity in all actionable guidance.
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 Core (Windows-centric frameworks) in its code samples, providing them before other stacks. The only explicit mention of how to access the client certificate in a framework is for ASP.NET, and the detailed code samples for certificate validation are heavily focused on C# and .NET. There is no mention of Linux-specific tools, shell commands, or configuration patterns, and no examples are given for Linux command-line environments (e.g., Bash). The Azure CLI example is cross-platform, but there are no Linux-specific troubleshooting steps, nor is there any mention of Linux-specific certificate handling nuances. The documentation assumes familiarity with Windows development patterns and tools.
Recommendations
- Add explicit Linux/Bash command-line examples for enabling client certificates and configuring exclusion paths, in addition to Azure CLI.
- Provide guidance or examples for accessing and validating client certificates in popular Linux web servers (e.g., Nginx, Apache) when running on App Service for Linux.
- Include troubleshooting steps or notes for Linux-specific issues, such as file permissions or environment variable handling.
- Balance the order of code samples by presenting cross-platform or Linux-friendly stacks (Node.js, Python, Java) before or alongside Windows-centric frameworks.
- Clarify that the Azure CLI is cross-platform and can be used from Bash or other Linux shells.
- Mention any differences in client certificate handling between App Service on Windows and App Service on Linux, if applicable.
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 scripting in the automation section, mentioning PowerShell before Azure CLI, and lacking explicit Linux or cross-platform command-line examples. There are no Linux-specific instructions or screenshots, and the automation section does not provide Bash or shell script equivalents, which may disadvantage Linux users.
Recommendations
- Provide Linux/Bash shell script examples alongside PowerShell in the automation section.
- Ensure Azure CLI examples are given equal prominence and detail as PowerShell, and consider listing CLI before PowerShell to avoid 'windows_first' bias.
- Include references or links to Linux-specific configuration guides where appropriate, especially in sections that mention language-specific guides.
- Add screenshots or instructions that reflect both Windows and Linux environments where user interaction with the OS is relevant.
- Review terminology and workflow steps to ensure they are not specific to Windows tools or patterns unless necessary, and clarify when instructions are cross-platform.
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 providing PowerShell instructions and examples first, referencing Visual Studio (a primarily Windows tool) for setup, and using PowerShell-specific modules. While an Azure CLI example is included, the initial focus and tooling are Windows-centric, and there is no explicit mention of Linux environments or parity in tooling/setup.
Recommendations
- Provide explicit Linux/macOS instructions and examples, including shell commands and environment-specific notes.
- Mention cross-platform tools (such as VS Code or Azure CLI) before or alongside Windows-specific tools like Visual Studio.
- Ensure that all PowerShell scripts have equivalent Bash or shell script examples, and clarify which steps are platform-agnostic.
- Highlight any differences or considerations for Linux users, such as authentication methods or environment setup.
- Consider reordering examples so that cross-platform or Linux-native instructions are presented before or alongside Windows/PowerShell examples.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based CLI examples for per-app scaling, with no equivalent examples for Linux users (e.g., Azure CLI/bash). The use of PowerShell cmdlets and Windows-centric scripting patterns is exclusive, and there is no mention of cross-platform or Linux-native tools. The ordering and focus on PowerShell also implicitly prioritize Windows workflows.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell code snippets, using bash syntax to support Linux and macOS users.
- Explicitly mention that both PowerShell and Azure CLI can be used, and provide guidance for both environments.
- Where possible, use cross-platform tools and scripting patterns in documentation examples.
- Consider including a table or section comparing PowerShell and Azure CLI commands for common per-app scaling tasks.
- Review related documentation links to ensure Linux and cross-platform resources are also referenced.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command requires an extra flag. In the automation section, Azure PowerShell is given equal prominence to Azure CLI, which is more cross-platform, but PowerShell is traditionally associated with Windows. Throughout, the Azure portal (a web UI) is used, which is platform-neutral, but there are no explicit Linux shell or scripting examples beyond the CLI. There are no Linux-specific tools or shell script examples, and PowerShell (a Windows-centric tool) is featured as a primary automation option.
Recommendations
- Present Linux and Windows options in parallel, or alternate which is listed first to avoid 'windows_first' ordering.
- Provide Bash shell scripting examples for automation, especially for Linux users, in addition to Azure CLI and PowerShell.
- Clarify that Azure CLI is cross-platform and recommend it as the default for scripting, with PowerShell as an alternative.
- Where possible, include Linux-native tooling or workflows, such as Bash scripts or integration with Linux package managers.
- Explicitly state that all examples work on both Windows and Linux unless there are platform-specific caveats.
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
Summary
The documentation demonstrates subtle Windows bias by listing Windows SKU availability before Linux, referencing Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and using Windows terminology (e.g., 'Windows SKU', 'Azure PowerShell') without equal emphasis on Linux-native tools or shell environments. While Linux is mentioned and supported, examples and instructions are not always presented with Linux parity or in a Linux-first manner.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their order to avoid always listing Windows first.
- Include Bash or shell script automation examples in addition to Azure CLI and PowerShell, especially for Linux users.
- Clarify that Azure CLI commands are cross-platform and can be run natively on Linux, macOS, and Windows.
- Where PowerShell is referenced, mention that PowerShell Core is cross-platform, or provide equivalent Bash commands.
- Use neutral terminology (e.g., 'Platform SKU availability') instead of 'Windows SKU availability' unless a distinction is necessary.
- Explicitly state Linux support and provide Linux-specific guidance where platform differences exist.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias, particularly in the guidance for identifying impacted Azure Traffic Manager endpoints. The only provided script for this scenario is a PowerShell script, with explicit instructions for downloading and running it in PowerShell. There are no equivalent Bash, Azure CLI, or cross-platform alternatives, and no mention of how Linux or Mac users should proceed. Elsewhere, examples and instructions focus on REST API and Azure CLI, which are cross-platform, but the only concrete script-based automation is Windows-centric.
Recommendations
- Provide a Bash or Azure CLI script alternative for identifying non-Azure Traffic Manager endpoints, or at least mention how Linux/Mac users can achieve the same result.
- When referencing scripts, clarify platform compatibility and offer guidance for non-Windows users.
- Where possible, prefer Azure CLI or REST API examples for automation tasks, as these are cross-platform.
- Explicitly state if a scenario or tool is only supported on Windows, and provide a workaround or alternative for Linux/Mac users.
- Consider including a table or section summarizing all available tools/scripts for each OS.
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 explicit scripting example in the 'Automate with scripts' section, with no corresponding Bash or Linux shell script. Additionally, while Azure CLI is mentioned, it is only linked and not shown inline, and the PowerShell example is presented more prominently. There are no Linux-specific instructions or screenshots, and the workflow assumes use of the Azure Portal or Windows-centric tools, with no mention of Linux command-line workflows or file handling (e.g., .pfx file creation on Linux).
Recommendations
- Add explicit Bash/Azure CLI script examples inline, similar to the PowerShell example.
- Include Linux-specific guidance for certificate creation, upload, and management (e.g., using OpenSSL to create .pfx files on Linux).
- Ensure that screenshots and instructions are not Windows-centric; consider including Linux terminal screenshots or notes.
- Present Azure CLI and Bash examples before or alongside PowerShell to avoid a 'Windows-first' impression.
- Reference Linux documentation or workflows where relevant, such as for inspecting headers or configuring HTTPS in Linux-hosted apps.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-per-app.md
...blob/main/articles/app-service/manage-scale-per-app.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for per-app scaling, referencing Azure PowerShell cmdlets exclusively, and omitting equivalent CLI or scripting instructions for Linux users. There are no Bash, Azure CLI, or cross-platform examples, and the PowerShell approach is presented first and exclusively, which may disadvantage users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI (az) examples for all PowerShell commands to support Linux and macOS users.
- Include Bash script examples for configuring per-app scaling where appropriate.
- Present cross-platform (CLI or ARM template) approaches before or alongside PowerShell to avoid the impression of Windows-first tooling.
- Explicitly mention that all operations can be performed from any OS using Azure CLI or ARM templates, not just PowerShell.
- Consider adding a table or section comparing PowerShell and CLI commands for common tasks.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-diagnostics.md
...blob/main/articles/app-service/overview-diagnostics.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing several features and tools that are either exclusive to Windows apps or are described in detail only for Windows. Sections such as 'Investigation of application code problems', 'Proactive CPU monitoring', 'Proactive auto-healing', and 'Navigator' are marked as Windows-only, with no Linux equivalents or alternatives discussed. Linux support is mentioned only in passing, and there are no Linux-specific troubleshooting examples or screenshots. This may leave Linux users with less guidance and fewer actionable steps.
Recommendations
- Provide Linux-specific troubleshooting steps and examples, especially for diagnostics and advanced tools.
- Where a feature is Windows-only, explicitly mention Linux alternatives or workarounds, or clarify if there is no equivalent.
- Include screenshots and walkthroughs for Linux-based App Service apps, not just Windows.
- Ensure parity in documentation by highlighting which diagnostic tools and features are available for Linux, and link to relevant Linux documentation where appropriate.
- Consider a comparison table summarizing feature availability and differences between Windows and Linux App Service environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-webjobs.md
...ocs/blob/main/articles/app-service/overview-webjobs.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 Windows-centric tools and workflows, such as Visual Studio deployment to Windows App Service, without providing equivalent Linux examples or explicitly mentioning Linux deployment options. References to Kudu and Visual Studio are present, but there is no guidance for Linux users or parity in deployment tooling and monitoring.
Recommendations
- Add explicit examples and instructions for deploying WebJobs to Linux-based App Service plans, including command-line (CLI) and cross-platform tooling.
- Provide parity in deployment guidance by including VS Code, Azure CLI, and GitHub Actions examples that work on both Windows and Linux.
- Clarify which features (such as Kudu or Visual Studio deployment) are available or different on Linux App Service plans.
- Include Linux-specific troubleshooting and monitoring guidance, such as using App Service diagnostics or log streaming, especially where Kudu is not available.
- Ensure that references to Windows-specific tools (like Visual Studio) are balanced with cross-platform alternatives.