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 276-300 of 2121 flagged pages
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-dotnetcore.md .../articles/app-service/configure-language-dotnetcore.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows instructions and tools (such as Visual Studio, Kudu, CMD/PowerShell) are introduced first or given more prominence. Windows-specific tools and patterns (Kudu, Advanced Tools, PowerShell) are mentioned before their Linux equivalents, and Visual Studio is referenced as the primary publishing tool. While Linux instructions are present and reasonably detailed, Windows examples and terminology often appear first or are more familiar to users of Windows environments.
Recommendations
  • Balance the order of presentation: Alternate or randomize the order of Windows and Linux pivots to avoid always presenting Windows first.
  • Provide parity in tooling references: For every mention of Windows tools (Kudu, PowerShell, Visual Studio), ensure Linux equivalents (SSH, Bash, VS Code, CLI) are mentioned with equal detail and prominence.
  • Expand Linux-specific examples: Where Windows instructions reference GUI tools (e.g., Visual Studio), provide equivalent Linux workflows (e.g., using VS Code, CLI, or other Linux-friendly IDEs).
  • Clarify cross-platform applicability: When describing concepts (such as deployment or configuration), explicitly state how they apply to both Windows and Linux, and avoid language that implies Windows is the default or preferred platform.
  • Add more Linux troubleshooting and diagnostic guidance: Match the detail level of Windows troubleshooting sections with Linux-specific advice and tools.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-language-nodejs.md ...main/articles/app-service/configure-language-nodejs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows instructions and tools (such as IISNode and web.config) are often presented first or exclusively, with Linux alternatives appearing later or in separate sections. PowerShell is referenced for instrumentation, while Linux-specific troubleshooting and configuration details are less prominent or omitted. Some examples, such as remote debugging and Application Insights instrumentation, mention Windows/PowerShell approaches before Linux equivalents, and certain Windows-specific tools (IISNode, web.config) are described in detail, whereas Linux alternatives are less emphasized.
Recommendations
  • Ensure Linux instructions/examples are presented alongside Windows ones, or alternate which platform is shown first in each section.
  • Provide Linux equivalents for all Windows-specific tools and configuration files (e.g., explain how to handle startup configuration and error troubleshooting in Linux containers, not just web.config for Windows).
  • Include Linux-specific troubleshooting scenarios and solutions, similar to the detailed Windows troubleshooting section.
  • Add parity for instrumentation and monitoring instructions (e.g., show how to enable Application Insights via CLI or portal for Linux, not just PowerShell for Windows).
  • Where PowerShell is referenced, also provide Bash or Azure CLI examples for Linux users.
  • Expand on Linux container-specific features, such as startup scripts, environment variable management, and logging, to match the detail given to Windows/IISNode.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-ssl-bindings.md ...ob/main/articles/app-service/configure-ssl-bindings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by providing PowerShell automation examples but omitting equivalent Linux shell (Bash/Azure CLI) scripts. The 'Automate with scripts' section lists PowerShell after Azure CLI, but only includes a code sample for PowerShell, not for Bash or Linux environments. There are no explicit Linux-specific workflow or tool references, and the documentation does not provide parity in examples for Linux users.
Recommendations
  • Add Bash/Azure CLI script examples alongside PowerShell in the 'Automate with scripts' section.
  • Ensure all automation steps have both Windows (PowerShell) and Linux (Bash/CLI) equivalents, with code samples for each.
  • Reference Linux-specific configuration guides or workflows where relevant, especially in sections discussing certificate upload and management.
  • Explicitly mention cross-platform compatibility for steps involving local certificate files, noting differences in file handling between Windows and Linux.
  • Review related content to ensure Linux and cross-platform resources are included and highlighted equally.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting Windows-specific instructions, code samples, and certificate store usage before Linux equivalents. Windows certificate store access is explained in detail with C# and Java examples, while Linux guidance is limited and deferred. Non-Windows languages (Node.js, PHP, Python) are referenced only generically, with no concrete examples. Windows tools and patterns (certificate store, environment variables, user profile loading) are emphasized, and Linux instructions are less prominent and less detailed.
Recommendations
  • Provide Linux-first or parallel examples for certificate access in all supported languages (C#, Java, Node.js, PHP, Python), not just C#.
  • Include explicit Linux code samples for Java, Node.js, PHP, and Python, showing how to load certificates from file paths and environment variables.
  • Balance the explanation of certificate stores and file-based access between Windows and Linux, ensuring both platforms are covered with equal depth.
  • Avoid referencing Windows tools and patterns (e.g., certificate store, user profile loading) before Linux equivalents; present both approaches side-by-side.
  • Expand the 'Load a certificate from a file' section to include concrete Linux examples and best practices for securing certificates on Linux.
  • Clarify environment variable usage for Linux containers, with examples in multiple languages.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (IIS, Certreq.exe) are mentioned for certificate export, and PowerShell is given as a primary automation example alongside Azure CLI. There are references to Windows-specific scenarios (e.g., Windows container apps for outbound calls with private CA certificates), and Linux equivalents (such as Linux container support or Linux-specific certificate management patterns) are not discussed or are missing. In automation and scripting, PowerShell is presented as a main option, with no mention of Bash scripts or Linux-native approaches. The order of examples and FAQs tends to present Windows scenarios first or exclusively.
Recommendations
  • Add explicit Linux examples for certificate export and management, such as using OpenSSL commands for all relevant scenarios.
  • Include Bash scripting examples for automating certificate binding and management, not just Azure CLI and PowerShell.
  • Clarify support and limitations for Linux-based App Service apps and containers, especially in sections discussing outbound calls and trusted root store modifications.
  • When listing automation options, present Azure CLI and Bash first, or equally with PowerShell, to avoid Windows-first ordering.
  • Reference Linux tools (e.g., keytool, OpenSSL) wherever Windows tools (IIS, Certreq.exe) are mentioned, and provide links to Linux documentation.
  • Add notes or tables clarifying feature parity between Windows and Linux App Service environments for certificate scenarios.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-authentication-types.md ...in/articles/app-service/deploy-authentication-types.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by listing Windows-centric tools (PowerShell, Visual Studio, Visual Studio Code) prominently and providing references and examples for these tools. PowerShell is given a dedicated row, and Visual Studio/VS Code are highlighted as deployment methods, with multiple reference links. There is no mention of Linux-specific deployment tools (such as Bash scripts, SCP, SFTP, rsync, or Linux-native CI/CD pipelines), nor are there examples or documentation links for Linux command-line usage. The order of presentation and reference documentation favors Windows tools and workflows, while Linux alternatives are missing.
Recommendations
  • Add examples and documentation links for Linux-native deployment methods (e.g., Bash scripts, SCP, SFTP, rsync).
  • Include references to Linux command-line usage for Azure CLI, showing parity with PowerShell examples.
  • Mention and provide documentation for Linux-based CI/CD tools (e.g., Jenkins, GitLab CI) where relevant.
  • Balance the presentation order so that Linux and Windows tools are given equal prominence.
  • Clarify that Azure CLI is cross-platform and provide explicit Linux usage examples.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-continuous-deployment.md ...n/articles/app-service/deploy-continuous-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. The 'External Git' section specifically mentions 'For Windows apps', implying that manual continuous deployment setup is primarily for Windows. There is no equivalent mention or guidance for Linux apps. References to Kudu (a tool historically associated with Windows App Service) are present, but there is no discussion of Linux-specific deployment patterns or troubleshooting. No examples or instructions are given for Linux environments, and Windows terminology is used without Linux parity.
Recommendations
  • Add explicit guidance and examples for Linux-based App Service apps, especially in the 'External Git' section.
  • Clarify whether manual continuous deployment steps apply to both Windows and Linux apps, or provide separate instructions if needed.
  • Include troubleshooting and deployment notes relevant to Linux environments, such as differences in build providers, file permissions, or runtime behaviors.
  • Avoid language that implies features or steps are Windows-only unless truly exclusive, and provide Linux alternatives or parity where possible.
  • Reference Linux-native tools or patterns (e.g., SSH, Bash scripts) alongside Kudu and Windows-centric approaches.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides detailed Azure PowerShell instructions, including multiple steps and notes, while the Azure CLI section is brief and limited to a single command. There is a strong emphasis on PowerShell, a Windows-centric tool, with no mention of Linux shell scripting or alternative Linux-native tools. The order of presentation also places PowerShell after CLI, but the PowerShell section is much more comprehensive, suggesting a bias towards Windows tooling and workflows.
Recommendations
  • Expand the Azure CLI section to include step-by-step instructions equivalent to those provided for PowerShell, such as checking subnet delegation and configuring integration.
  • Include Linux shell scripting examples (e.g., Bash) for tasks like parameter preparation and resource checks.
  • Mention cross-platform compatibility explicitly for both Azure CLI and PowerShell, clarifying how Linux and macOS users can perform these tasks.
  • Add troubleshooting or advanced configuration examples using Linux-native tools where applicable.
  • Ensure parity in detail and guidance between CLI and PowerShell sections to avoid favoring Windows users.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. Windows tools and patterns (Visual Studio, WinSCP, PowerShell) are mentioned first or exclusively, with no explicit Linux command-line examples or Linux-native FTP clients referenced. PowerShell is given its own section, but there is no equivalent for Bash or Linux shell scripting. The troubleshooting and client recommendations also focus on Windows tools, and there are no instructions for using Linux CLI utilities (such as lftp, ftp, or curl) for FTP/S deployment.
Recommendations
  • Add explicit Linux command-line examples for connecting and deploying via FTP/S (e.g., using lftp, ftp, curl, or ncftp).
  • Mention Linux-native FTP clients (such as FileZilla, gFTP, or Nautilus) alongside Windows tools.
  • Provide Bash or shell script equivalents for PowerShell commands, especially for extracting endpoints and configuring FTPS state.
  • Ensure that examples and tool recommendations are presented in a cross-platform order or grouped by OS, rather than Windows-first.
  • Include troubleshooting steps relevant to Linux environments, such as firewall configuration or SELinux/AppArmor considerations.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-local-git.md ...ocs/blob/main/articles/app-service/deploy-local-git.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions, but PowerShell examples and workflows are given significant prominence, including automatic remote creation and troubleshooting notes referencing Windows-specific errors. The troubleshooting section mentions Windows-native module errors and MSBuild (Windows tool) before Linux equivalents. There is no explicit mention of Linux-specific tools, patterns, or troubleshooting, and PowerShell is featured as a primary workflow, which is Windows-centric. The Git Credential Manager dialog is referenced without clarifying cross-platform differences.
Recommendations
  • Add explicit Linux terminal examples and workflows, such as Bash or zsh, alongside PowerShell instructions.
  • Include troubleshooting notes for Linux-specific errors (e.g., native module build failures on Linux, permissions issues).
  • Mention Linux equivalents for tools like MSBuild (e.g., dotnet CLI for .NET Core on Linux) and clarify platform-specific behaviors.
  • Clarify that Git Credential Manager may behave differently on Linux/macOS, and provide guidance for credential handling on those platforms.
  • Ensure that examples and instructions do not assume Windows as the default environment; present CLI/Bash instructions first or equally with PowerShell.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-staging-slots.md ...blob/main/articles/app-service/deploy-staging-slots.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all operations, with PowerShell examples and references present throughout. Windows-specific tools and configuration patterns (such as Web.config and applicationInitialization) are referenced without Linux alternatives. The warm-up and troubleshooting sections rely on Windows-centric concepts (Web.config, IIS, D:\home\LogFiles), and there is no mention of Linux-specific deployment patterns, troubleshooting paths, or configuration files. Additionally, auto swap is noted as unsupported on Linux, but no Linux alternatives or workarounds are suggested.
Recommendations
  • Add explicit Linux-specific instructions and examples, especially for troubleshooting, warm-up, and configuration (e.g., using app settings or startup scripts instead of Web.config/applicationInitialization).
  • Reference Linux file paths and logging locations alongside Windows paths (e.g., /home/LogFiles/eventlog.xml).
  • Clarify differences in slot swap behavior and limitations for Linux-based web apps, and suggest workarounds or alternatives where features are unsupported.
  • Provide parity in tooling examples, such as Bash scripts or Linux-native automation approaches, and highlight any differences in Azure CLI usage on Linux.
  • Where PowerShell is referenced, also mention Bash or other Linux shell equivalents, and ensure documentation does not assume Windows/IIS-centric deployment patterns.
  • Include troubleshooting steps and error log locations for Linux-based App Service environments.
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: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing Azure PowerShell examples for configuring Traffic Manager and App Service Environments. There are no CLI (az), Bash, or Linux-oriented instructions, and PowerShell is presented as the default and only method for resource management. This may disadvantage users working on Linux or macOS, who are more likely to use Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, showing how to create and configure Traffic Manager profiles and endpoints using CLI.
  • Include Bash script snippets where appropriate, especially for DNS lookups and other command-line operations.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and provide links to both sets of documentation.
  • Reorder examples or provide parallel instructions so that Linux/macOS users do not feel secondary to Windows users.
  • Add a section or note on cross-platform tooling, clarifying which steps can be performed on Linux, macOS, and Windows.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/deploy-zip.md ...zure-docs/blob/main/articles/app-service/deploy-zip.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific paths (e.g., D:\home\site\wwwroot) are mentioned before Linux equivalents, and the Kudu UI ZIP deploy workflow is described as unavailable for Linux, with no Linux-specific alternative workflow detailed. Azure PowerShell examples are provided for most deployment scenarios, but PowerShell is not supported for key Linux scenarios (e.g., deploying individual files or to network-secured apps), and this limitation is only briefly noted. The documentation frequently references Windows-centric tools and patterns (Kudu UI, PowerShell), while Linux-native tools or workflows (such as SCP, SFTP, rsync, or bash scripts) are not discussed or exemplified. Overall, Linux users are left with less guidance and fewer tailored examples.
Recommendations
  • Provide Linux-specific deployment workflow examples, especially where the Kudu UI is unavailable (e.g., step-by-step FTP/SFTP/SCP/rsync instructions for Linux apps).
  • Ensure Linux paths and deployment nuances are mentioned first or equally alongside Windows equivalents.
  • Include bash script examples for automating deployments on Linux, and reference Linux-native tools where appropriate.
  • Clarify limitations of PowerShell for Linux scenarios and offer alternative approaches for Linux users.
  • Add troubleshooting tips and best practices specifically for Linux App Service deployments.
  • Where features/tools are Windows-only (e.g., Kudu UI ZIP deploy), offer clear Linux alternatives and document them in detail.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing PowerShell as the first and most detailed scripting example, referencing Visual Studio (a Windows-centric tool) for deployment, and using Azure PowerShell modules. Although an Azure CLI example is included, the prominence and order of Windows/PowerShell tools and patterns suggest a preference for Windows environments. There are no explicit Linux shell (bash) or cross-platform editor references, and the CLI example is less detailed.
Recommendations
  • Provide Linux/bash shell examples alongside PowerShell, especially for scripting tasks.
  • Reference cross-platform deployment tools (e.g., VS Code, GitHub Actions) in addition to Visual Studio.
  • Ensure Azure CLI examples are as detailed and prominent as PowerShell examples.
  • Explicitly mention platform compatibility for all steps and scripts.
  • Add notes or links for Linux users regarding prerequisites and environment setup.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview.md .../azure-docs/blob/main/articles/app-service/overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: Windows-specific tools and patterns (COM, registry, MSI, drive mapping, PowerShell scripts, RDP) are described in detail, especially for the Managed Instance preview, with no Linux equivalents or examples. PowerShell is mentioned as the scripting method for configuration, and Windows workloads (.NET, Java) are listed explicitly, while Linux support is only referenced as 'not supported' for Managed Instance. Command-line tools are listed together, but Azure PowerShell is named alongside Azure CLI, with no Linux-specific shell or scripting examples. The documentation gives Windows features and patterns first and in more detail, while Linux is only mentioned as an alternative or exclusion.
Recommendations
  • Provide equivalent Linux examples and tooling for configuration and deployment (e.g., Bash scripts, Linux shell commands) where PowerShell is mentioned.
  • Include Linux-specific features, patterns, and troubleshooting steps alongside Windows ones, especially in sections describing advanced or legacy scenarios.
  • List Linux support and container options with equal prominence and detail as Windows features, not only as exclusions.
  • Add examples of deploying and managing Linux workloads, including references to Linux file systems, permissions, and diagnostic tools.
  • Clarify which features are cross-platform and which are Windows-only, and provide links to Linux documentation where relevant.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-hosting-plans.md ...ob/main/articles/app-service/overview-hosting-plans.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the 'Managed Instance on Azure App Service (preview)' section, which exclusively describes Windows-specific features, tools, and use cases (e.g., PowerShell scripts, RDP, IIS customization, .NET Framework). There are no Linux equivalents or examples provided, and the preview feature is explicitly unavailable for Linux or containers. Throughout the page, examples and advanced features are described in a Windows-centric manner, with no parity or guidance for Linux users.
Recommendations
  • Add equivalent Linux-focused examples and features, such as Bash scripting, SSH access, and Linux-specific runtime support.
  • Explicitly mention Linux limitations and roadmap for parity in preview features like Managed Instance.
  • Provide guidance and documentation for Linux container workloads, including scaling, networking, and OS customization.
  • Ensure that links and feature tables include both Windows and Linux options, and avoid presenting Windows-only features without Linux context.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/reference-app-settings.md ...ob/main/articles/app-service/reference-app-settings.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: Windows-specific paths, tools, and configuration patterns are frequently mentioned first or exclusively (e.g., 'D:\home', 'applicationHost.config', IIS, Web Deploy/MSDeploy, w3wp.exe, .bat files, Windows time zones). Many environment variables and settings reference Windows conventions, with Linux equivalents often missing, less detailed, or described after the Windows version. Some examples and defaults are given only for Windows, and Windows-centric troubleshooting and behaviors are emphasized. Linux-specific settings are present but less thoroughly explained, and Linux examples are often omitted or referenced only in passing.
Recommendations
  • Provide Linux-specific examples and paths alongside Windows ones throughout the documentation (e.g., '/home' as well as 'D:\home').
  • Ensure that for every Windows tool or pattern mentioned (such as Web Deploy/MSDeploy, IIS, applicationHost.config), the Linux equivalent (such as Oryx, Apache/nginx config, deployment scripts) is described with equal detail and prominence.
  • Add Linux-focused troubleshooting guidance and behavioral notes where Windows-specific ones are given (e.g., for process crashes, warmup paths, file locking issues).
  • When listing environment variables, clearly indicate applicability (Windows, Linux, or both) and avoid defaulting to Windows-centric terminology or examples.
  • Include parity in language-specific sections (e.g., for Java, Node.js, PHP, Ruby), ensuring Linux settings and conventions are as thoroughly documented as Windows ones.
  • Reference Linux time zone documentation and conventions in addition to Windows time zones.
  • Avoid using Windows-only file extensions or command syntax in examples unless also providing Linux alternatives.
  • Consider restructuring sections so that Linux and Windows are presented in parallel tabs or columns, rather than Windows-first.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-instance.md ...main/articles/app-service/overview-managed-instance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows-specific features and patterns. All examples and configuration mechanisms reference Windows tools (PowerShell, registry, MSI, IIS, RDP, GAC, MSMQ), with no Linux equivalents or parity. The page consistently prioritizes Windows terminology and does not provide Linux-based examples, guidance, or alternatives, even in sections discussing general capabilities or best practices.
Recommendations
  • Add equivalent Linux-focused documentation or explicitly state Linux limitations and roadmap.
  • Provide Bash or shell script examples for configuration, alongside PowerShell.
  • Mention Linux alternatives to Windows tools (e.g., systemd for services, Linux file system mounts, SSH for remote access).
  • Clarify which features are Windows-only and suggest Linux-native approaches where possible.
  • Include a comparison table showing feature parity and gaps between Windows and Linux managed instances.
  • Offer migration guidance for Linux workloads, or link to relevant Linux App Service documentation.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-webjobs.md ...s/blob/main/articles/app-service/quickstart-webjobs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows samples and tools first, providing more Windows-specific script types (CMD, Batch, PowerShell, F#), and including Windows-only scripting options that have no Linux equivalents. The Linux section is shorter and lacks parity for certain scripting languages (e.g., PowerShell, Batch, CMD, F#). Windows tools and patterns (such as PowerShell and batch scripting) are mentioned exclusively or before Linux alternatives.
Recommendations
  • Present Windows and Linux instructions and samples in parallel, rather than listing Windows first.
  • Add Linux equivalents for scripting languages where possible (e.g., PowerShell Core for Linux, F# scripts, or note their absence).
  • Explicitly state which samples are not available for Linux and why, to avoid confusion.
  • Include Linux-first or cross-platform examples where possible, such as using Bash or Python as the default demonstration.
  • Balance the number of sample types between Windows and Linux, or clarify platform limitations.
  • Avoid using Windows-specific terminology or tools (e.g., PowerShell, CMD, Batch) without mentioning Linux alternatives or their lack thereof.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-app-access-sql-database-as-user-dotnet.md ...utorial-connect-app-access-sql-database-as-user-dotnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation displays a Windows bias by referencing Windows-specific tools (SQL Server Management Studio, Integrated Windows authentication) and patterns before mentioning or providing alternatives for Linux. Examples for connecting to SQL Database use Windows-centric tools and do not offer Linux equivalents (e.g., Azure Data Studio, sqlcmd on Linux, or cross-platform authentication flows). The tutorial assumes Visual Studio and Git Bash, but does not mention Linux-native editors or deployment methods. There are no explicit Linux command-line or tool examples for database management or local debugging.
Recommendations
  • Include examples using cross-platform tools such as Azure Data Studio and sqlcmd on Linux/macOS.
  • Provide instructions for local debugging and deployment using Linux-native editors (e.g., VS Code, JetBrains Rider) and CLI workflows.
  • Mention Linux authentication patterns and clarify differences with Windows authentication, including Kerberos and other protocols.
  • Add screenshots or walkthroughs for Linux environments where applicable.
  • Ensure parity in troubleshooting steps by referencing Linux-compatible tools and environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjob-types.md ...es/app-service/includes/webjobs-create/webjob-types.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation presents Windows file types and tools (cmd, bat, exe, PowerShell) in greater detail and with more examples than Linux equivalents. Windows examples are more comprehensive, listing multiple file types and runtimes, while Linux sections are brief and only mention shell scripts and one runtime example. There is a clear emphasis on Windows-specific tools and patterns, with Linux support described minimally.
Recommendations
  • Expand the Linux sections to list all supported file types and runtimes, similar to the Windows sections (e.g., mention support for .py, .js, .jar, etc. where applicable).
  • Provide Linux-specific examples for each supported language/runtime, not just shell scripts.
  • Avoid listing Windows tools and file types first; consider parallel structure or presenting Linux and Windows options side-by-side.
  • Clarify that runtimes for various languages are available on both platforms, if true, and specify any differences.
  • Ensure parity in detail and structure between Windows and Linux documentation tabs.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjobs-supported-platforms.md ...includes/webjobs-create/webjobs-supported-platforms.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation lists Windows hosting options before Linux, and Windows-specific file types (.exe, .cmd, .bat) and PowerShell scripts (.ps1) are mentioned before Bash scripts and other cross-platform languages. This ordering and emphasis suggest a subtle Windows bias, prioritizing Windows tools and patterns over Linux equivalents.
Recommendations
  • List Linux hosting options and file types before or alongside Windows options to avoid implicit prioritization.
  • Provide equal emphasis to Linux-native tools (e.g., Bash scripts) and mention them before or alongside Windows tools.
  • Include examples for both Windows and Linux platforms when demonstrating usage.
  • Explicitly state cross-platform compatibility and highlight any differences or limitations between Windows and Linux environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-backup.md ...e-docs/blob/main/articles/app-service/manage-backup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific paths (e.g., %HOME%, D:\home\site\wwwroot) and terminology are used throughout, often without Linux equivalents or with Linux mentioned secondarily. Examples for file exclusion and backup filters use Windows-style paths and directories. The Kudu DebugConsole and FTP instructions reference Windows file systems. Automation mentions Azure PowerShell before providing parity with Azure CLI, and PowerShell samples are linked separately. There are no explicit Linux shell or tool examples, and Linux-specific nuances (such as file paths or permissions) are not addressed in backup/restore procedures.
Recommendations
  • Provide Linux-specific examples and instructions alongside Windows ones, especially for file paths (e.g., /home/site/wwwroot) and backup filter files.
  • Clarify platform differences in all relevant sections, such as file system structure, access methods, and environment variables.
  • Include Linux shell (bash) automation samples and reference Linux-native tools where appropriate.
  • Ensure that all CLI instructions and screenshots demonstrate both Windows and Linux scenarios, or note any differences explicitly.
  • Avoid using Windows terminology (e.g., D:\home) as the default; present both Windows and Linux paths in parallel.
  • Expand troubleshooting and error message sections to include Linux-specific issues and solutions.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-dotnet-deploy-vs.md .../main/articles/app-service/webjobs-dotnet-deploy-vs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily focused on Windows development environments, specifically Visual Studio, and does not mention or provide examples for Linux or cross-platform workflows. All instructions, screenshots, and tooling references assume the use of Visual Studio on Windows, with no guidance for Linux users or alternative development tools. There is no mention of deploying or developing WebJobs from Linux, nor are command-line or VS Code workflows discussed.
Recommendations
  • Add instructions and examples for developing and deploying WebJobs from Linux environments, including using the Azure CLI, VS Code, or other cross-platform tools.
  • Include screenshots and step-by-step guides for Linux users, such as using dotnet CLI, zip deployment, or GitHub Actions.
  • Explicitly mention cross-platform support and clarify which steps are Windows-specific.
  • Provide parity in examples by listing Linux/macOS alternatives alongside Visual Studio steps, or link to relevant documentation.
  • Highlight any limitations or differences in the WebJobs development and deployment experience between Windows and Linux.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-sidecar-multi-container-apps.md ...es/app-service/migrate-sidecar-multi-container-apps.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by requiring PowerShell for both script-based and manual migration steps, providing only PowerShell examples for tasks like base64 decoding, and referencing a migration script that is exclusively a PowerShell (.ps1) script. There are no equivalent Linux shell (bash) or cross-platform examples for these operations, and Linux tools/patterns are not mentioned. The prerequisites list PowerShell first, reinforcing the Windows-centric approach.
Recommendations
  • Provide bash or shell script equivalents for all PowerShell commands, especially for base64 decoding and running migration scripts.
  • Offer a cross-platform migration script (e.g., in Python or bash) or document how Linux/macOS users can perform the migration without PowerShell.
  • List prerequisites in a neutral order and clarify which tools are required for each platform.
  • Include explicit Linux/macOS instructions and examples alongside Windows/PowerShell ones.
  • Reference Linux-native tools (e.g., base64, curl, jq) where appropriate.
GitHub Create Pull Request
← Previous Page 12 of 85 Next →