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 951-975 of 2121 flagged pages
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a bias towards Windows environments by providing only C# code examples (which are most commonly used on Windows), referencing the Microsoft.IdentityModel.Tokens NuGet package, and not mentioning or providing examples for Linux or cross-platform tools/languages (such as OpenSSL, Python, or Node.js) for generating JWTs. There are no CLI or scripting examples for Linux/macOS users, and the documentation assumes a Windows/.NET development environment.
Recommendations
  • Add examples for generating and signing the JWT client secret using cross-platform tools such as OpenSSL, Python (e.g., PyJWT), or Node.js (e.g., jsonwebtoken).
  • Provide command-line instructions for Linux/macOS users, such as using OpenSSL to handle the .p8 key and generate signatures.
  • Mention and link to cross-platform libraries and tools for JWT creation, not just .NET/NuGet packages.
  • Include a note clarifying that the process can be completed on any OS, and provide parity in examples for both Windows and Linux/macOS environments.
  • If referencing application settings or file editing, mention relevant editors and commands for Linux/macOS as well as Windows.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias primarily in the 'Scenario 2: Site is an Azure Traffic Manager "nested" or "external" endpoint' section, where only a PowerShell script is provided for identifying impacted Traffic Manager profiles. There are no equivalent Bash, Azure CLI, or cross-platform script examples for Linux or macOS users. The instructions for running the script assume a Windows/PowerShell environment, and there is no mention of Linux-compatible alternatives or guidance for non-Windows users.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for Linux/macOS users to identify impacted Traffic Manager profiles.
  • When referencing scripts or tools, offer both PowerShell and cross-platform (Bash/CLI) alternatives, or clearly indicate if a solution is Windows-only.
  • Explicitly mention cross-platform compatibility or provide guidance for running PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
  • Review all example commands and ensure parity between Windows and Linux environments, especially for common administrative tasks.
  • Consider adding a table or section summarizing available tools/scripts for each platform to help users quickly find relevant instructions.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows evidence of Windows bias. Windows is mentioned first in SKU 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 (bash) or scripting examples, and the use of PowerShell is not contextualized for Linux users. Portal instructions and screenshots do not clarify differences for Linux vs. Windows app deployments. The documentation also refers to 'Development tools' and 'Clone app' features without noting any OS-specific differences or limitations.
Recommendations
  • Present Linux and Windows instructions/examples in parallel, or alternate which comes first.
  • Provide bash shell scripting examples alongside PowerShell for automation, especially for Linux users.
  • Clarify any OS-specific differences in portal workflows, screenshots, or feature availability.
  • Explicitly mention if PowerShell commands are cross-platform or provide alternatives for Linux/macOS.
  • Ensure all automation and scripting sections include both Azure CLI and native Linux shell (bash/zsh) usage where applicable.
  • Highlight any limitations or differences for Linux users in 'Development tools' or 'Clone app' features.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-run-package.md ...s/blob/main/articles/app-service/deploy-run-package.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias by referencing Windows directory paths (e.g., D:\home\site\wwwroot) before Linux equivalents, using Windows-style path separators, and omitting explicit Linux/Bash command examples. The instructions and troubleshooting sections focus on Windows directory structures and do not provide Linux-specific guidance or parity in examples.
Recommendations
  • Provide Linux directory paths (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections, and ensure Linux paths are mentioned first or equally.
  • Include explicit Linux/Bash command examples where appropriate, especially for file operations or manual deployment steps.
  • Clarify when instructions or behaviors differ between Windows and Linux App Service plans, and provide platform-specific notes as needed.
  • Use platform-neutral language and path separators (e.g., <project-root>/app_data/jobs/...) or provide both Windows and Linux variants.
  • Add troubleshooting steps and examples that address Linux-specific scenarios, such as file permissions or directory structures.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS web servers within VMware environments, which are Windows-centric technologies. There is no mention of Linux-based hosting environments (such as Kestrel, Apache, or Nginx), nor are there examples or guidance for discovering .NET apps running on Linux servers. All discovery capabilities and resources are described in the context of Windows tools and patterns.
Recommendations
  • Include information on discovering .NET web apps hosted on Linux servers, such as those running Kestrel, Apache, or Nginx.
  • Provide parallel examples or workflows for Linux-based environments, including any differences in appliance setup or discovery processes.
  • Mention whether Azure Migrate supports Linux-hosted .NET apps and, if so, provide links or references to relevant documentation.
  • Clarify in the introduction that the current guidance is Windows/IIS-specific, and direct Linux users to appropriate resources if available.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/app-service-app-service-environment-geo-distributed-scale.md ...-service-app-service-environment-geo-distributed-scale.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples for configuring Traffic Manager and App Service Environments. There are no equivalent examples using Azure CLI, Bash, or ARM templates, which are more commonly used in Linux or cross-platform environments. The reliance on PowerShell commands and references to PowerShell-based tooling may alienate users working on Linux or macOS, or those who prefer command-line tools that are natively cross-platform.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell scripts shown, ensuring Linux and macOS users can follow along without needing PowerShell.
  • Include Bash shell command examples where appropriate, especially for DNS lookups or domain configuration steps.
  • Reference ARM/Bicep templates or Terraform for infrastructure-as-code alternatives that are platform-agnostic.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide links to relevant cross-platform tooling.
  • Reorder or parallelize example sections so that non-Windows approaches are presented alongside or before Windows-specific tooling.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily focused on Windows-based Node.js applications running on Azure App Service, specifically with iisnode. All configuration, troubleshooting, and examples are tailored to Windows environments, referencing Windows-specific tools (e.g., iisnode, web.config, named pipes, Win32 error codes, Kudu CMD/PowerShell). There are no Linux or cross-platform equivalents or examples provided, and Linux troubleshooting or deployment patterns are not mentioned.
Recommendations
  • Add a parallel section or separate guide for Node.js on Azure App Service Linux, covering best practices, configuration, and troubleshooting.
  • Provide Linux-specific examples for profiling, debugging, and monitoring (e.g., using pm2, systemd, Linux file paths, and logs).
  • Reference Linux equivalents for configuration (e.g., environment variables, process managers) and troubleshooting (e.g., using SSH, Linux shell, log locations).
  • Avoid assuming the presence of Windows-only tools (like iisnode, web.config, Win32 error codes) and instead offer cross-platform or Linux-native alternatives.
  • When presenting examples or recommendations, either provide both Windows and Linux versions or clearly indicate which platform each applies to, with links to the other.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-certificate-in-code.md ...icles/app-service/configure-ssl-certificate-in-code.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias: Windows-specific instructions, code samples, and certificate store usage are presented before Linux equivalents. Most code examples (C#, Java) focus on Windows certificate stores, with Linux guidance often deferred or less detailed. There are references to Windows tools and patterns (e.g., certificate store, environment variables, .NET Framework specifics) without equivalent Linux or cross-platform alternatives. Non-Windows languages (Node.js, PHP, Python) are not given direct examples, and Linux-specific instructions are less prominent or detailed.
Recommendations
  • Provide Linux examples alongside Windows examples, not after them or as an afterthought.
  • Include code samples for loading certificates in popular Linux languages (Node.js, Python, PHP, Java) directly in the documentation.
  • Present Linux and Windows instructions in parallel sections or tabs, ensuring parity in detail and clarity.
  • Avoid referencing Windows certificate store patterns exclusively; explain Linux certificate handling (e.g., file-based, OpenSSL, environment variables) with equal depth.
  • When mentioning environment variables or file paths, always provide both Windows and Linux equivalents together.
  • Ensure that all steps (such as making certificates accessible, loading them in code, and updating/renewing) have explicit Linux instructions, not just references to 'see respective language documentation.'
GitHub 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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows instructions for configuring data sources in Tomcat and JBoss on Azure App Service. However, in the Tomcat server-level configuration section, the Windows instructions are more detailed and prominent, with a heavy reliance on PowerShell scripts and Windows-specific tools and environment variables. The Windows approach is described with step-by-step PowerShell scripting, while the Linux approach uses shell scripts and standard Linux tools, but with less detail and explanation. Additionally, Windows-specific patterns (such as copying Tomcat to a local directory and using %LOCAL_EXPANDED%) are described at length, and PowerShell is the default scripting language for Windows, with no mention of alternatives.
Recommendations
  • Ensure that Linux and Windows instructions are presented with equal detail and clarity, including step-by-step explanations and troubleshooting tips for both platforms.
  • Provide equivalent Linux shell script examples wherever PowerShell scripts are shown for Windows, and vice versa.
  • Avoid presenting Windows instructions or tools (such as PowerShell) before Linux equivalents unless there is a clear reason; consider parallel presentation or Linux-first ordering if usage data supports it.
  • Highlight cross-platform tools and approaches (e.g., Azure CLI, bash scripts, or platform-agnostic configuration methods) where possible.
  • Explicitly mention any differences in capabilities or limitations between Windows and Linux, so users can make informed decisions.
  • Include links to Linux and Windows documentation in all relevant sections to ensure discoverability.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing Azure Storage Explorer with a Windows-specific tab in the SAS generation link and not providing equivalent Linux-native tooling or CLI examples for file upload and SAS generation. There are no explicit Linux or cross-platform instructions for uploading files or generating SAS tokens, and the only GUI tool mentioned is typically associated with Windows environments.
Recommendations
  • Provide explicit CLI-based instructions (using az storage blob upload and az storage blob generate-sas) for uploading files and generating SAS tokens, which work cross-platform.
  • Mention and link to Linux/macOS versions of Azure Storage Explorer, or clarify its cross-platform availability.
  • Avoid linking to documentation with Windows-specific tabs by default; either use a neutral tab or include both Windows and Linux/macOS instructions.
  • Consider including examples using common Linux tools (e.g., curl, azcopy) for file upload and SAS generation.
  • Add a note or section highlighting cross-platform compatibility and alternative tools for Linux users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-container-azure-pipelines.md ...ticles/app-service/deploy-container-azure-pipelines.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on deploying Windows containers, with all examples, variables, and instructions referencing Windows-specific images, pools, and App Service types. There are no examples or guidance for deploying Linux containers, and the use of 'windows-latest' as the default agent pool and 'webAppHyperVContainer' as the app type further reinforce a Windows-centric approach. Linux equivalents and cross-platform options are not mentioned or demonstrated.
Recommendations
  • Add parallel examples and instructions for deploying Linux containers, including YAML snippets using 'ubuntu-latest' as the vmImage and 'webAppLinux' as the appType.
  • Explicitly mention that Azure App Service supports both Windows and Linux containers, and provide guidance for choosing between them.
  • Include a section or callout explaining differences in deployment steps, variables, and supported features between Windows and Linux container deployments.
  • Ensure that all variable and task names are platform-agnostic or provide both Windows and Linux variants.
  • Consider restructuring the documentation to present both Windows and Linux options side-by-side, or provide a platform selection at the beginning.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnet-framework.md ...les/app-service/configure-language-dotnet-framework.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based deployment and configuration patterns for ASP.NET apps. Examples and instructions reference Windows tools (such as Visual Studio, Kudu, CMD, and PowerShell) and Windows file paths, with no equivalent Linux or cross-platform guidance. There are no Linux-specific examples or mentions of how these tasks would differ or be accomplished on Linux-based App Service plans.
Recommendations
  • Add explicit guidance and examples for configuring and deploying ASP.NET apps on Linux-based App Service plans, including relevant command-line examples and file paths.
  • When showing how to inspect .NET Framework versions, include Linux equivalents or clarify that these steps are Windows-only, and provide Linux alternatives if available.
  • Balance references to Windows tools (Visual Studio, Kudu, CMD, PowerShell) with Linux-friendly alternatives (such as VS Code, Bash, SSH, or Linux-based Kudu/console).
  • Clearly indicate when a step or feature is only available on Windows App Service, and provide links or notes for Linux users.
  • Consider reordering or parallelizing instructions so that Linux and Windows approaches are presented side-by-side, rather than Windows-first or Windows-only.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-github-actions/deploy-github-actions-publish-profile.md ...ithub-actions/deploy-github-actions-publish-profile.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides cross-platform deployment examples for most stacks (ASP.NET Core, Java, Tomcat, Node.js, Python) using Ubuntu runners, but the ASP.NET (classic) example exclusively uses a Windows runner and Windows-specific tools (NuGet, MSBuild) without offering a Linux alternative or mentioning cross-platform options. This prioritizes Windows for ASP.NET scenarios and omits Linux parity for that stack.
Recommendations
  • Add a Linux-based example for ASP.NET (classic) deployment, using Mono or .NET SDK for cross-platform builds if possible.
  • Explicitly mention when a workflow requires Windows-only tools (e.g., MSBuild for full .NET Framework) and provide guidance or links for Linux alternatives or limitations.
  • Where possible, provide both Windows and Linux workflow examples side-by-side for stacks that can be built on both platforms.
  • Clarify in the ASP.NET section why Windows is required (if so), and suggest migration paths to .NET Core/5+ for better cross-platform support.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-ftp.md ...zure-docs/blob/main/articles/app-service/deploy-ftp.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows-centric tools and workflows, such as PowerShell and WinSCP, and by providing PowerShell examples alongside Azure CLI, but not Linux shell or SFTP examples. Windows tools (e.g., Visual Studio, WinSCP) are mentioned before or instead of cross-platform or Linux-native alternatives. There are no explicit Linux shell command examples or references to Linux FTP clients, and the documentation does not address Linux-specific usage patterns.
Recommendations
  • Add Linux shell command examples (e.g., using lftp, curl, or ftp) for connecting and deploying via FTP/S.
  • Include Linux-native FTP/S clients (e.g., FileZilla, lftp, gFTP) alongside or before Windows tools like WinSCP and Visual Studio.
  • Provide bash or shell script equivalents for PowerShell commands, especially for extracting FTP/S endpoints from Azure CLI output.
  • Ensure that cross-platform tools and instructions are presented before or alongside Windows-specific tools.
  • Mention SFTP (if supported) or clarify its status for Linux users, as it is a common secure file transfer method on Linux.
  • Explicitly state that the instructions apply to both Windows and Linux, and highlight any OS-specific differences or considerations.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/deploy-intelligent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md ...ent-apps/deploy-intelligent-apps-linux-dotnet-pivot.md
High Priority View Details →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows/Visual Studio tooling and workflows, such as right-clicking in Solution Explorer and using the NuGet package manager in Visual Studio, without providing equivalent Linux or cross-platform instructions. There are no explicit Linux command-line examples or references to Linux-native editors or workflows. The only CLI reference is to the .NET CLI for NuGet, but it is secondary to the Visual Studio/Windows-first approach.
Recommendations
  • Provide explicit Linux and cross-platform instructions for file creation and editing, such as using the 'dotnet new page' command or editing files with VS Code, nano, or vim.
  • List CLI-based package installation (dotnet CLI) before or alongside Visual Studio/NuGet Package Manager instructions, and clarify that both work on Windows, Linux, and macOS.
  • Include screenshots or terminal commands for Linux environments where relevant, such as setting environment variables or deploying to App Service from a Linux shell.
  • Avoid instructions that assume a GUI file explorer (e.g., 'Right-click the Pages folder') and instead offer command-line alternatives.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide parity in examples and tooling references.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation exhibits a moderate Windows bias. While it does provide some cross-platform guidance (notably OpenSSL for certificate export), it frequently references Windows-specific tools (IIS, Certreq.exe), and in automation examples, PowerShell is given equal or more prominence than Linux-native alternatives. There is a lack of explicit Linux or macOS-specific instructions for common certificate management tasks, and Windows tooling is mentioned before or instead of Linux equivalents.
Recommendations
  • For every mention of Windows tools (IIS, Certreq.exe), provide equivalent Linux/macOS instructions (e.g., using OpenSSL, certbot, or native Linux commands) and reference them with equal prominence.
  • In automation sections, always provide both Azure CLI and Azure PowerShell examples, and consider listing Azure CLI (which is cross-platform) first.
  • Where screenshots or UI steps are shown, clarify if there are OS-specific differences, or note that the steps are OS-agnostic.
  • Add explicit guidance for Linux and macOS users for certificate generation, export, and upload, including common command-line workflows.
  • In FAQ and troubleshooting, address Linux-specific scenarios (e.g., trusted root store management in Linux containers) where relevant.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific UI actions (e.g., 'Right click', 'click Save'), using tooling and patterns familiar to Windows users (such as SQL Server Management Studio paradigms and ADO.NET connection strings), and omitting explicit Linux or cross-platform command-line instructions. There are no Linux-specific examples, terminal commands, or guidance for users developing or deploying from Linux environments. The documentation assumes a GUI-based workflow and does not mention or show parity for Linux users, despite the 'linux-related-content' tag.
Recommendations
  • Include Linux-specific or cross-platform instructions for all steps, such as using the dotnet CLI, VS Code, or command-line editors instead of GUI actions like 'Right click'.
  • Provide examples for connecting to Azure SQL from Linux environments, including using the Azure CLI, sqlcmd, or Data Studio on Linux.
  • When referencing connection strings or authentication, clarify how to obtain and use these on Linux (e.g., environment variables, .NET user secrets, or Key Vault integration).
  • Add explicit Linux terminal commands for package installation, file creation, and deployment steps.
  • Avoid Windows-centric language (e.g., 'click Save') or provide alternative instructions for Linux users.
  • Highlight any cross-platform tools (like Azure Data Studio or VS Code) and show their usage on Linux.
  • If using code snippets that assume Windows file paths or conventions, provide Linux equivalents.
GitHub Create Pull Request
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 →
Scanned: 2025-08-16 00:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias, especially in the .NET and Python sections. Windows tools (Visual Studio, Azure PowerShell) are listed before or more prominently than Linux equivalents. There are more detailed or explicit references to Windows-based development environments and tools, while Linux or cross-platform options are less emphasized or sometimes missing. The 'Next step' call-to-action also defaults to an ASP.NET (Windows-centric) workflow.
Recommendations
  • Ensure Linux and cross-platform tools (e.g., VS Code, CLI, Azure CLI) are listed before or alongside Windows-specific tools in all language stacks.
  • Provide explicit Linux examples and links for all stacks, especially for .NET and Python, where Windows tools and environments are currently prioritized.
  • Balance references to Windows tools (e.g., Visual Studio, PowerShell) with equivalent Linux tools (e.g., VS Code, Azure CLI, Bash).
  • For 'Next step' actions, offer a choice of stack or highlight a cross-platform/language-neutral workflow instead of defaulting to ASP.NET.
  • Audit all quickstart and tutorial links to ensure Linux instructions are present and as detailed as Windows instructions.
GitHub Create Pull Request
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 →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 3 bias types
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, where only a PowerShell script is provided to identify non-Azure endpoints. There are no equivalent Bash, Azure CLI, or cross-platform alternatives offered. Throughout the page, when command-line guidance is given, REST API and Azure CLI references are present, but in the one scenario requiring scripting, only PowerShell is mentioned, with no Linux/macOS-compatible example. This may disadvantage users on Linux or macOS who do not have access to PowerShell or prefer Bash scripting.
Recommendations
  • Provide a Bash or Azure CLI script alternative to the PowerShell script for identifying non-Azure Traffic Manager endpoints, or at least mention how Linux/macOS users can achieve the same result.
  • When referencing scripts or automation, offer both Windows (PowerShell) and Linux/macOS (Bash/CLI) examples to ensure parity.
  • Explicitly state if a solution is Windows-only and provide guidance for non-Windows users.
  • Consider linking to cross-platform tools or scripts, or provide guidance on running PowerShell Core on Linux/macOS if no alternative exists.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-migration-discover-net.md ...cles/app-service/app-service-migration-discover-net.md
High Priority View Details →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively discusses discovery of ASP.NET web apps on IIS web servers within VMware environments, which are all Windows-centric technologies. There is no mention of Linux-based web servers (such as Apache or Nginx), nor are there examples or guidance for discovering .NET apps hosted on Linux. All references, capabilities, and linked resources focus on Windows tools and patterns.
Recommendations
  • Include guidance and examples for discovering .NET web apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
  • Mention whether Azure Migrate supports Linux-based .NET app discovery, and if not, clarify this limitation.
  • Add parity in documentation by providing Linux-specific instructions, tooling, and troubleshooting steps.
  • Reference Linux migration resources and tools alongside Windows/IIS examples.
  • Explicitly state platform support and any differences in discovery capabilities between Windows and Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, specifically Azure App Service on Windows with iisnode. All configuration and troubleshooting steps reference Windows-specific tools, paths (e.g., node.exe, web.config, named pipes, Win32 error codes), and workflows (Kudu, PowerShell, CMD). There are no Linux equivalents or examples, and Linux-based deployment or troubleshooting is not mentioned. Windows terminology and tools are used exclusively or introduced first throughout the document.
Recommendations
  • Add equivalent sections or links for Linux-based Azure App Service (e.g., using PM2, NGINX, or other process managers instead of iisnode/IIS).
  • Provide Linux-specific troubleshooting steps, including log file locations, process management, and error handling.
  • Include examples using Bash or Linux shell commands alongside or instead of PowerShell/CMD.
  • Reference Linux file paths and configuration files where appropriate (e.g., /home/site/wwwroot, /var/log).
  • Clarify at the start that the guide is Windows-specific, and link to a Linux-focused guide if available.
  • Where possible, generalize best practices to be cross-platform and call out platform-specific differences in dedicated sections.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md ...ain/articles/app-service/app-service-best-practices.md
High Priority View Details →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows subtle Windows bias by referencing Windows-specific tools (such as web.config and iisnode) without providing equivalent Linux alternatives or explanations. Some configuration and troubleshooting guidance assumes a Windows-based environment, and Linux-specific instructions are either missing or mentioned only as an aside.
Recommendations
  • For features like auto-healing, provide Linux-native configuration options (e.g., app settings, environment variables, or Linux-specific config files) alongside web.config guidance.
  • When referencing iisnode or web.config for Node.js apps, include information about how to configure these settings in Linux containers or App Service for Linux, such as using PM2 or environment variables.
  • Ensure that all examples and troubleshooting steps are presented for both Windows and Linux environments, or clarify when a feature is Windows-only.
  • Where Windows tools or patterns are mentioned, explicitly provide Linux equivalents and place them with equal prominence in the documentation.
  • Audit the documentation for other implicit Windows assumptions and address them to ensure Linux users have clear, actionable guidance.
GitHub Create Pull Request
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 →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. While both Windows and Linux are mentioned as supported platforms, and Azure CLI examples (which are cross-platform) are provided, there is a consistent pattern of presenting Windows-related information and tools first. For example, the SKU availability section lists 'Windows' before 'Linux', and the automation section provides Azure PowerShell (a Windows-centric tool) as a primary scripting option, without mentioning Bash or Linux shell scripting. There are no Linux-specific command-line or scripting examples beyond the Azure CLI, and the PowerShell example is not paralleled with a Linux shell script.
Recommendations
  • Present Linux and Windows options in parallel, or alternate which is listed first to avoid implicit prioritization.
  • When providing automation examples, include both Azure PowerShell and Bash/shell script examples to ensure parity for Linux users.
  • Where screenshots or portal steps are shown, note any differences for Linux-based App Service plans if applicable.
  • Explicitly state that Azure CLI commands are cross-platform and suitable for both Windows and Linux users.
  • Consider adding a section or callout for Linux users, highlighting any platform-specific considerations or best practices.
GitHub Create Pull Request
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 →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows a mild Windows bias. In several places, Windows is mentioned before Linux (e.g., in availability descriptions and SKU checks). Both Azure CLI and PowerShell scripting are covered, but PowerShell (a Windows-centric tool) is given its own section, while no Linux shell scripting (e.g., Bash) or automation examples are provided. The portal instructions and screenshots are Windows-oriented, and there is no mention of Linux-specific tools or workflows beyond a single CLI flag.
Recommendations
  • Provide Linux shell (Bash) scripting examples for automation, not just Azure CLI and PowerShell.
  • Ensure Linux is mentioned alongside Windows, not after, in all availability and feature descriptions.
  • Add guidance or screenshots for Linux users where portal UI or tooling may differ.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • If referencing PowerShell, consider also referencing Bash or other common Linux scripting environments for parity.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-dotnet-sqldatabase.md ...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority View Details →
Scanned: 2025-08-15 00:01
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily oriented toward Windows and Visual Studio on Windows. All instructions, screenshots, and tool references assume the user is on Windows, using Visual Studio, and deploying to Azure App Service (Windows). There are no examples or instructions for Linux users, command-line alternatives, or cross-platform development environments. PowerShell and Windows-specific tools (e.g., Package Manager Console, SQL Server Object Explorer) are used exclusively, with no mention of Bash, Azure CLI, or VS Code.
Recommendations
  • Add parallel instructions and screenshots for Linux/macOS users, including using VS Code or JetBrains Rider as alternative IDEs.
  • Include Azure CLI and Bash command examples for all steps currently shown with PowerShell or Visual Studio UI.
  • Provide guidance for deploying to Azure App Service (Linux) in addition to (Windows), and explain differences if any.
  • Reference cross-platform tools (e.g., Azure Data Studio instead of SQL Server Object Explorer) for database management.
  • Clarify which steps are Windows-specific and provide alternatives for non-Windows environments.
  • Ensure all code/package installation steps have cross-platform equivalents (e.g., dotnet CLI for package management).
GitHub Create Pull Request
← Previous Page 39 of 85 Next →