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 1126-1150 of 2121 flagged pages
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/webjobs-sdk-how-to.md ...s/blob/main/articles/app-service/webjobs-sdk-how-to.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily through the exclusive use of Windows-style file paths (e.g., c:\data\import) in configuration examples, references to Windows-specific .NET APIs (such as WinHttpHandler and ServicePointManager), and the absence of explicit Linux or cross-platform command-line or file path examples. There are no mentions of Linux-specific tools, shell commands, or file system conventions, and all examples assume a Windows environment by default.
Recommendations
  • Provide Linux and macOS equivalents for all file path examples (e.g., use /home/user/data/import alongside c:\data\import).
  • When referencing .NET APIs that have platform-specific behavior (like WinHttpHandler or ServicePointManager), clarify their cross-platform compatibility or provide alternatives for Linux environments.
  • Include notes or examples for setting environment variables and configuration files using Linux/macOS shell syntax (e.g., export VAR=value, or editing ~/.bashrc).
  • Explicitly state that the SDK and its configuration are cross-platform, and provide guidance for running and debugging WebJobs on Linux/macOS.
  • Where relevant, mention any differences in behavior or limitations when running on non-Windows platforms.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by providing installation instructions using Visual Studio's Package Manager Console (PowerShell-based) and referencing Visual Studio UI paths. While the .NET Core CLI is cross-platform, the Package Manager Console and Visual Studio instructions are Windows-centric, and there are no explicit Linux or non-Windows environment examples or guidance. The documentation assumes the use of Visual Studio, which is primarily a Windows tool, and omits parity for Linux development environments (e.g., VS Code, JetBrains Rider, or plain CLI usage on Linux/Mac).
Recommendations
  • Add explicit instructions for Linux and macOS users, such as using the .NET CLI for all package installations and project management tasks.
  • Avoid referencing Visual Studio-specific tools (like the Package Manager Console) as primary or only options; if included, present cross-platform CLI instructions first.
  • Mention and provide examples for popular cross-platform editors (e.g., VS Code) and how to perform equivalent tasks outside Visual Studio.
  • Clarify that all .NET CLI commands work identically on Linux, macOS, and Windows, and provide terminal/shell instructions for non-Windows users.
  • Where UI navigation is described (e.g., Visual Studio menus), offer alternative steps for CLI or other IDEs.
  • Include a note or section on developing and running the sample on Linux/macOS, highlighting any differences or prerequisites.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-performance-degradation.md ...es/app-service/troubleshoot-performance-degradation.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows-specific tools (such as PowerShell, IIS diagnostics, and SysInternals Procdump), providing instructions and links that are Windows-centric (e.g., .NET Profiler for Windows), and omitting equivalent Linux-based troubleshooting steps or examples. The Kudu Console section highlights PowerShell and DOS commands, but does not mention Bash or Linux shell usage. There is a lack of parity in examples and guidance for Linux-based App Service environments.
Recommendations
  • Include Linux-specific troubleshooting steps and examples, such as using Bash in the Kudu Console, and mention Linux-compatible diagnostic tools.
  • Provide links and instructions for enabling diagnostics and profiling on Linux-based App Service plans (e.g., Application Insights Profiler for Linux, or alternatives).
  • When referencing PowerShell or Windows tools, also provide equivalent Bash/CLI commands and Linux-native tools where possible.
  • Clarify when a feature or tool is Windows-only, and offer Linux alternatives or workarounds.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or clearly indicate which applies to which environment.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-diagnostic-logs.md ...n/articles/app-service/troubleshoot-diagnostic-logs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias by providing more detailed instructions, features, and examples for Windows-based App Service apps. Several logging features (web server logging, detailed error messages, failed request tracing) are described only for Windows, with no Linux equivalents or alternatives mentioned. Windows-specific tools and log formats (e.g., W3C, Log Parser, Web.config) are referenced, while Linux-native patterns or tools are absent. Linux instructions are less detailed and sometimes limited to basic file system logging, with no mention of advanced diagnostics or parity with Windows features.
Recommendations
  • Provide equivalent Linux examples and instructions for all logging features, or clearly state if a feature is unavailable on Linux.
  • Describe Linux-native logging and diagnostic tools (e.g., journalctl, syslog, or container log collection patterns) where applicable.
  • Include parity tables or feature comparison charts to clarify which logging features are available on Windows vs. Linux.
  • Avoid referencing only Windows tools (like Log Parser or Web.config) without suggesting Linux alternatives.
  • Expand Linux sections to match the detail and troubleshooting guidance given for Windows, including advanced diagnostics and error tracing where possible.
  • If certain features are Windows-only, suggest best-practice workarounds or third-party tools for Linux users.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-domain-ssl-certificates.md ...es/app-service/troubleshoot-domain-ssl-certificates.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It provides a Windows-specific DNS cache clearing command (ipconfig /flushdns) without mentioning the Linux/macOS equivalent. In the FAQ, PowerShell is referenced for moving resources, but no CLI or Linux-native alternative is given. There are no Linux-specific tools, commands, or troubleshooting steps, and Windows patterns are mentioned first or exclusively in relevant sections.
Recommendations
  • When providing command-line instructions (e.g., clearing DNS cache), include Linux/macOS equivalents such as 'sudo systemd-resolve --flush-caches' or 'sudo killall -HUP mDNSResponder' for macOS.
  • When referencing PowerShell cmdlets (e.g., Move-AzResource), also provide the Azure CLI equivalent (e.g., 'az resource move ...') and note cross-platform compatibility.
  • Where troubleshooting steps involve tools or commands, ensure parity by mentioning both Windows and Linux/macOS approaches.
  • Consider adding a section or callouts for Linux/macOS users where platform-specific steps may differ.
  • Review for any other Windows-centric language or assumptions and revise to be more platform-neutral.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-dotnet-visual-studio.md ...icles/app-service/troubleshoot-dotnet-visual-studio.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 workflows, with all examples and instructions assuming the use of Visual Studio on Windows. There are no examples or guidance for Linux-based development environments, cross-platform tools, or command-line alternatives. Windows-specific tools (e.g., Server Explorer, File Explorer, IIS/Log Parser) are referenced exclusively, and there is no mention of Linux equivalents or how to perform these tasks outside of Visual Studio or on non-Windows platforms.
Recommendations
  • Add equivalent instructions and examples for Linux and macOS users, including how to perform remote debugging, log streaming, and file access using cross-platform tools such as VS Code, Azure CLI, and Kudu.
  • Include command-line examples (e.g., using Azure CLI, PowerShell Core, or Bash) for enabling diagnostics, downloading logs, and managing App Service configurations.
  • Reference and provide instructions for cross-platform editors (such as VS Code) and tools, not just Visual Studio on Windows.
  • Mention and link to Linux-friendly log analysis tools (e.g., grep, awk, jq, or open-source log viewers) as alternatives to Windows tools like Log Parser.
  • Clearly indicate which features are only available in Visual Studio on Windows and suggest alternatives or workarounds for users on other platforms.
  • Reorder sections or provide parallel instructions so that Linux/macOS approaches are not always secondary or omitted.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-webjobs.md ...ocs/blob/main/articles/app-service/tutorial-webjobs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windowscode Links
Summary
The documentation demonstrates a mild Windows bias, primarily by referencing Windows-specific concepts and links (such as 'windowscode' tabs and file type documentation), and by presenting .NET (historically Windows-centric) as the first and most detailed example. There is also a subtle preference for Windows terminology and documentation structure, even though the code and packaging examples themselves are cross-platform and use Bash scripts for execution.
Recommendations
  • Provide explicit Linux and Windows instructions or clarify when steps are cross-platform, especially in the .NET section.
  • Avoid linking only to 'windowscode' tabs for supported file types and CRON expressions; provide Linux-specific or neutral links where possible.
  • Ensure parity in depth and clarity across all language pivots, not just .NET.
  • Explicitly mention when a step is platform-agnostic or, if not, provide both Windows and Linux alternatives (e.g., for packaging, running, or scripting).
  • Consider adding a section or note about differences in WebJobs behavior or deployment between Windows and Linux App Service plans, if applicable.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-custom-container.md ...main/articles/app-service/tutorial-custom-container.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. The Windows section is presented first and in greater detail, with step-by-step instructions that rely heavily on Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts). The Windows workflow is tightly coupled to the Visual Studio GUI and Windows file management patterns, with no mention of equivalent Linux or cross-platform approaches for those steps. There is no guidance for performing the Windows scenario from a non-Windows environment, and the Linux section is entirely separate, with no cross-references or parity in application scenario (the Windows example is ASP.NET with custom fonts, while the Linux example is a generic Django/Flask app). There are also missing Linux equivalents for certain steps (e.g., installing custom fonts in a Linux container, using PowerShell scripts for configuration).
Recommendations
  • Provide Linux or cross-platform equivalents for all steps shown in the Windows workflow, especially for application scenarios that require OS-level customization (e.g., installing fonts in a Linux container, not just Windows).
  • Avoid presenting Windows as the default or primary platform by giving equal prominence to both Windows and Linux pivots, or by starting with a neutral introduction.
  • Replace or supplement Windows-specific tooling (Visual Studio, Windows Explorer, PowerShell scripts) with cross-platform alternatives (VS Code, command-line instructions, Bash scripts) where possible.
  • For steps that require file installation or OS customization, show how to achieve the same result in a Linux container (e.g., using apt-get to install fonts, Bash scripts for automation).
  • Ensure that advanced scenarios (such as custom OS configuration, font installation, or other integrations) are demonstrated for both Windows and Linux, not just Windows.
  • Where PowerShell scripts are used, provide Bash equivalents for Linux users.
  • Explicitly mention any limitations or differences between Windows and Linux container support in App Service, and provide guidance for users migrating from either platform.
  • Consider using a consistent sample application or scenario across both pivots to better illustrate parity.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-security.md ...cs/blob/main/articles/app-service/overview-security.md
High Priority View Details →
Scanned: 2025-07-13 21:37
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 in several areas. In the 'Static IP restrictions' section, access restriction examples and configuration details are provided specifically for 'App Service on Windows', including references to the web.config file and IIS dynamic IP security, with no equivalent Linux guidance. There are no Linux-specific examples or mentions of how to achieve similar configurations on App Service for Linux, nor are cross-platform differences highlighted. Windows tools and patterns (e.g., web.config, IIS) are mentioned exclusively, and Linux is omitted from these discussions.
Recommendations
  • Provide equivalent examples and instructions for App Service on Linux wherever Windows-specific guidance is given (e.g., how to configure IP restrictions on Linux).
  • When referencing Windows-specific tools (such as web.config or IIS features), explicitly state their applicability and offer Linux alternatives (such as using .htaccess for Apache, nginx config, or App Service access restrictions via the Azure portal/CLI).
  • Ensure that cross-platform differences are clearly documented, and avoid presenting Windows as the default or only supported platform.
  • Add Linux-specific security configuration examples and clarify any limitations or differences in feature support between Windows and Linux App Service plans.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/environment/creation-terraform.md ...articles/app-service/environment/creation-terraform.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but it lists Azure CLI first (which is cross-platform) and then Azure PowerShell (which is Windows-centric). However, there are no explicit Linux shell (bash) examples for common tasks such as directory creation or environment variable export, and the PowerShell examples use Windows-style variable assignment. There is also no mention of Linux-specific tools or workflows, and no explicit guidance for Linux/macOS users in the setup or verification steps.
Recommendations
  • Add explicit bash/Linux shell examples for all steps involving command-line operations, such as directory creation, variable assignment, and running Terraform commands.
  • Clarify in the prerequisites or relevant sections that Azure CLI commands are cross-platform and provide bash syntax for variable assignment.
  • If PowerShell is included, also include equivalent bash commands for parity, especially for environment variable usage and output parsing.
  • Where file paths or command syntax may differ between Windows and Linux/macOS, provide notes or tabs for both environments.
  • Consider adding a 'Linux/macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' in the verification section to ensure all users are supported.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-custom-container.md ...ain/articles/app-service/configure-custom-container.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific instructions, tools, and examples (such as PowerShell commands, Windows base images, and Kudu/FTP access patterns) are often presented first or in more detail. Some advanced configuration sections (memory, CPU, health ping) are only described for Windows containers, with no Linux equivalents. While Linux content is present and there are Linux-specific pivots, parity in depth and clarity is lacking in several areas.
Recommendations
  • For every Windows-specific section (e.g., customizing memory, CPU, health ping), provide equivalent Linux container instructions or explicitly state if the feature is not supported for Linux.
  • When showing both Bash and PowerShell commands, present Bash (Linux) first or side-by-side, not always after PowerShell.
  • Ensure that advanced diagnostic and logging instructions (e.g., Kudu, FTP, log access) are equally detailed for Linux containers, not just Windows.
  • In sections about persistent storage, clarify differences and provide equal detail for both platforms, including Linux-specific caveats and best practices.
  • Where Windows parent images are listed, provide a similar list or guidance for recommended Linux base images.
  • Review all examples and ensure Linux tools and patterns (e.g., SSH, Linux file paths, Docker Compose) are as prominent as Windows ones.
  • Explicitly call out any features that are Windows-only, and provide links or alternatives for Linux users where possible.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-dotnetcore.md ...lob/main/articles/app-service/quickstart-dotnetcore.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented as the primary IDE for .NET Framework, and many screenshots and step-by-step instructions focus on Windows tools and UI. PowerShell is given a dedicated section, but Linux-specific PowerShell examples are commented out and not visible to users. In the PowerShell section, users are explicitly told to use Azure CLI for Linux, but no Linux PowerShell deployment steps are shown. File path examples (e.g., 'cd bin\Release\net8.0\publish') use Windows-style backslashes, and compressing/deploying steps are shown only for Windows. While cross-platform tools (Azure CLI, VS Code) are included, Windows patterns and tools are often mentioned first or exclusively, and Linux parity is not always achieved.
Recommendations
  • For every PowerShell deployment example, provide an equivalent Bash/Linux shell example, especially for steps like zipping and deploying files.
  • Uncomment and fully document the Linux PowerShell deployment steps, or remove PowerShell as a recommended tool for Linux if not supported.
  • When showing file paths or commands, provide both Windows and Linux syntax (e.g., use both '\' and '/').
  • Ensure that all screenshots and UI instructions that are Windows-specific are clearly labeled, and provide parallel instructions for macOS/Linux where possible.
  • In all sections, avoid language that implies Windows is the default or preferred platform; present cross-platform options equally and in parallel.
  • Expand the Azure CLI and VS Code sections to include more Linux/macOS-specific tips and troubleshooting.
  • Where possible, add explicit Linux/macOS instructions for tasks like compressing files (e.g., using 'zip' command) and deploying to App Service.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by frequently specifying features as 'Windows apps only' and providing more detailed descriptions for Windows-specific diagnostic tools (e.g., Proactive CPU monitoring, Proactive auto-healing, Navigator). Several advanced diagnostic features are described as available only for Windows apps, with Linux equivalents mentioned only briefly or not at all. There are no Linux-specific troubleshooting examples or step-by-step instructions, and Linux support is often described as limited or secondary.
Recommendations
  • Provide equivalent Linux examples and step-by-step instructions for diagnostic features wherever possible.
  • Clearly indicate feature parity or differences between Windows and Linux at the beginning of each relevant section.
  • Expand documentation for Linux-specific diagnostic tools and workflows, including screenshots and detailed usage guidance.
  • Where features are Windows-only, suggest alternative approaches or tools for Linux users.
  • Ensure that Linux and container scenarios are given equal prominence in feature descriptions and troubleshooting workflows.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/operating-system-functionality.md ...articles/app-service/operating-system-functionality.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page is heavily focused on Windows-based App Service environments. It describes file paths, environment variables, and system behaviors using Windows conventions (e.g., %SystemDrive%, c:\, d:\), references Windows-specific tools and frameworks (IIS, ASP.NET, COM, PowerShell), and omits equivalent Linux details or examples. Linux is mentioned only in a brief note, with no further explanation or parity in examples, environment variables, or operational behaviors.
Recommendations
  • Add parallel sections or callouts describing Linux App Service behaviors, including file system layout, environment variables (e.g., $HOME, /tmp), and storage persistence.
  • Provide Linux-specific examples alongside Windows ones, such as shell commands, file paths, and environment variable usage.
  • Clarify differences in diagnostic logging, process management, and network access for Linux containers, including supported tools and frameworks.
  • Avoid assuming Windows as the default; structure the documentation to address both Windows and Linux equally, or clearly indicate when content is Windows-specific.
  • Include links to Linux App Service documentation or quickstarts for readers interested in Linux environments.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-azure-database.md ...les/app-service/tutorial-connect-msi-azure-database.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, particularly in the 'Set up your dev environment' section, where Visual Studio for Windows is presented first and in greater detail than alternatives. Windows-specific tools (Visual Studio for Windows, Azure PowerShell) are mentioned explicitly and before their Linux/macOS equivalents. PowerShell is given its own section, and Windows-centric development environments are prioritized in the ordering of instructions. While Linux/macOS options are present, they are less emphasized and sometimes described in terms of their limitations (e.g., Visual Studio for Mac lacking integration).
Recommendations
  • Reorder the 'Set up your dev environment' section to present cross-platform or non-Windows options (such as Azure CLI and Visual Studio Code) before Windows-specific tools.
  • Provide equal detail and positive framing for Linux/macOS development environments, including Visual Studio Code and Azure CLI, rather than highlighting their limitations.
  • Include explicit examples or notes for common Linux/macOS shells (e.g., bash, zsh) where command-line instructions are given.
  • Avoid giving Windows tools (Visual Studio for Windows, PowerShell) their own sections unless parity is provided for Linux/macOS tools.
  • Where possible, mention open-source or cross-platform alternatives alongside Windows-specific tools, and ensure all code samples and instructions are validated on Linux/macOS as well as Windows.
GitHub 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 →
Scanned: 2025-07-13 21:37
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 Windows bias by exclusively providing PowerShell examples for per-app scaling configuration, without offering equivalent examples for Linux users (such as Azure CLI, Bash, or REST API). The use of PowerShell cmdlets and parameters is specific to Windows environments, and there is no mention of or guidance for Linux-native tools or workflows. The PowerShell section is presented before the ARM template section, reinforcing the Windows-first approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, demonstrating how to configure per-app scaling using cross-platform tools.
  • Include Bash or shell script snippets where appropriate to illustrate Linux workflows.
  • Explicitly mention that PowerShell examples can be run on Linux using Azure PowerShell, but provide native Linux alternatives for better parity.
  • Reorganize the documentation to present cross-platform (CLI/REST/ARM) approaches before or alongside PowerShell examples.
  • Clarify in the introduction that all major platforms are supported and provide links to relevant tooling for each.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/migrate-gateway-based-vnet-integration.md .../app-service/migrate-gateway-based-vnet-integration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides command-line examples for Azure CLI and Azure PowerShell, with PowerShell examples present for every operation. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its inclusion in parity with CLI can signal a Windows-centric approach. Furthermore, the documentation includes PowerShell examples before or alongside CLI, and does not mention or provide Linux-native shell (e.g., Bash) or scripting examples. There is also no explicit mention of Linux tooling or Linux-specific considerations, despite App Service supporting Linux workloads.
Recommendations
  • Clearly state that Azure CLI commands are fully supported on Linux, macOS, and Windows, and recommend CLI as the primary cross-platform tool.
  • Add explicit Bash shell script examples where relevant, or clarify that Azure CLI commands can be run in Bash or other Linux shells.
  • If PowerShell is included, clarify that Azure PowerShell is available cross-platform, but avoid implying it is required for Linux users.
  • Where platform-specific steps are necessary (e.g., for Linux or Windows containers), provide separate, clearly labeled instructions.
  • Review the order of examples: consider listing Azure CLI (cross-platform) before PowerShell to reinforce Linux parity.
  • Include troubleshooting or operational notes relevant to Linux environments, such as file permissions, shell differences, or integration caveats.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-patch-os-runtime.md ...main/articles/app-service/overview-patch-os-runtime.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-specific details, tools, and examples. It provides instructions and examples that are either exclusive to Windows (such as registry queries and references to Windows-specific files like web.config), or are presented only in the context of Windows App Service. There is a lack of equivalent Linux App Service instructions, examples, or references, and the documentation does not address how to obtain OS/runtime information or perform configuration on Linux-based App Service plans.
Recommendations
  • Add equivalent instructions and examples for Linux App Service, including how to query OS and runtime versions using Linux commands (e.g., cat /etc/os-release, lsb_release -a).
  • Clarify when instructions or examples are Windows-specific, and provide parallel Linux-specific guidance where applicable.
  • Include examples of configuration files and settings relevant to Linux (e.g., appsettings.json, environment variables, or startup scripts) alongside Windows examples like web.config.
  • Mention Linux-specific tools or methods (such as Bash, SSH, or Linux file paths) for accessing and managing App Service instances.
  • Ensure that tables and code samples are balanced, showing both Windows and Linux approaches where differences exist.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-storage.md ...cles/app-service/scenario-secure-app-access-storage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing installation instructions using the Visual Studio Package Manager Console (a Windows-centric tool) and referencing Visual Studio UI steps. The .NET Core CLI is mentioned, but the ordering and prominence of Windows/Visual Studio tooling is notable. There are no explicit Linux or cross-platform environment examples, nor are Linux-specific instructions or considerations provided.
Recommendations
  • Add explicit Linux/macOS instructions for installing the required NuGet packages, such as using the .NET CLI in a bash shell.
  • Reorder the installation instructions to present the cross-platform .NET CLI method before the Visual Studio/Windows-specific Package Manager Console.
  • Clarify that Visual Studio steps are Windows-specific and provide equivalent steps for popular Linux/macOS IDEs or editors (e.g., VS Code).
  • Include a note or section on running and deploying the sample code on Linux-based environments, such as Azure App Service for Linux or local Linux development.
  • Review all tooling references to ensure parity, avoiding exclusive mention of Windows tools where cross-platform alternatives exist.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/powershell-connect-to-sql.md ...icles/app-service/scripts/powershell-connect-to-sql.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell, which is traditionally a Windows-centric tool, and does not provide any equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI). All code samples, explanations, and cleanup instructions use PowerShell commands, and there is no mention of Linux tools or cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) examples for each PowerShell command, including setup, deployment, and cleanup steps.
  • Include a section or note explaining how to perform these tasks on Linux/macOS using Bash and Azure CLI.
  • Present both PowerShell and Azure CLI examples side-by-side or in tabs, so users can easily select their preferred environment.
  • Avoid assuming the user is on Windows or using PowerShell by default; clarify cross-platform options in the introduction.
  • Link to both PowerShell and Azure CLI documentation for further reference.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-vnet-integration.md ...main/articles/app-service/overview-vnet-integration.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific features and limitations (such as Windows Containers subnet sizing) are discussed in detail, while Linux-specific scenarios are only briefly mentioned (e.g., a single note about Linux continuous deployment network dependencies). There are no Linux-specific configuration examples or parity in troubleshooting or operational guidance. Windows terminology and patterns (such as references to Windows Server Active Directory, Windows Containers, and Kudu console UI) are used without equivalent Linux context or alternatives.
Recommendations
  • Add Linux-specific examples and guidance where Windows-specific details are provided (e.g., subnet sizing for Linux containers, Linux-specific environment variables, or troubleshooting steps).
  • Include Linux-focused operational notes, such as how to access environment variables or logs in Linux-based App Service environments.
  • Balance references to Windows tools (like Kudu console UI) with Linux equivalents (such as SSH or Azure CLI usage in Linux containers).
  • Where Windows limitations or features are discussed (e.g., Windows Server Active Directory domain join), explicitly mention Linux equivalents or note if not applicable.
  • Expand the Linux continuous deployment section to include more comprehensive guidance and examples, similar to the detail given for Windows Containers.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-resource-manager-templates.md ...cles/app-service/samples-resource-manager-templates.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page lists both Linux and Windows Azure App Service template samples, but there is a subtle bias towards Windows. Windows examples are often listed before Linux equivalents, and there are more detailed or varied Windows scenarios (e.g., Windows container, Windows with MySQL/PostgreSQL) compared to Linux. Some resource combinations are only shown for Windows, and there is no parity in example coverage for Linux (e.g., no Linux container example, no Linux app with Azure SQL Database). There are no command-line examples, so no PowerShell bias is present, but the pattern of presenting Windows first and more frequently is evident.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal coverage for each scenario (e.g., provide Linux container, Linux app with Azure SQL Database, Linux app with Redis, etc.).
  • Alternate the order of Linux and Windows examples or group them together to avoid always listing Windows first.
  • Where a scenario is only available for Windows, explicitly state this to avoid confusion.
  • Add missing Linux equivalents for all connected resource scenarios currently only shown for Windows.
  • Consider a dedicated section for Linux-specific templates to highlight parity and encourage cross-platform usage.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/powershell-deploy-staging-environment.md ...rvice/scripts/powershell-deploy-staging-environment.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses PowerShell for all examples and instructions, assumes the use of Azure PowerShell tooling, and does not mention or provide equivalent Bash, CLI, or Linux-native examples. All command references and cleanup instructions are PowerShell-specific, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Provide equivalent Azure CLI (az) script examples alongside PowerShell, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include Bash script samples for deployment and cleanup steps.
  • Mention both PowerShell and CLI installation guides, clarifying cross-platform support.
  • Structure the documentation to present both Windows (PowerShell) and Linux/macOS (CLI/Bash) options equally, or link to Linux-specific guides.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained, and provide installation instructions for those platforms.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-connect-msi-sql-database.md ...icles/app-service/tutorial-connect-msi-sql-database.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a Windows bias by prioritizing Windows and Visual Studio (Windows) workflows, providing PowerShell and sqlcmd examples without Linux alternatives, and omitting explicit Linux/macOS development environment instructions for key steps such as database permission grants. Linux and cross-platform tooling are mentioned only in passing or as secondary options, and there are no bash or Linux-native SQL client examples for database administration.
Recommendations
  • Provide explicit Linux/macOS equivalents for all command-line instructions, especially for database permission grants (e.g., using sqlcmd or Azure Data CLI on Linux).
  • Include examples using bash and cross-platform SQL clients (such as sqlcmd on Linux, Azure Data CLI, or Python-based tools) alongside PowerShell.
  • Reorganize sections so that cross-platform or Linux instructions are presented alongside or before Windows-specific instructions, rather than after.
  • Add a dedicated section or tab for Linux/macOS development environments, covering setup, authentication, and debugging workflows.
  • Ensure all tooling recommendations (e.g., for Visual Studio, Visual Studio Code, Azure CLI, Azure PowerShell) are presented with parity for Windows, Linux, and macOS.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/powershell-deploy-ftp.md .../articles/app-service/scripts/powershell-deploy-ftp.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell and Windows-centric tools and APIs (such as System.Net.FtpWebRequest), with no mention of Linux or cross-platform alternatives. All examples and cleanup instructions are provided only in PowerShell, and there are no Bash, Azure CLI, or Linux-native FTP tool examples. The focus on PowerShell and Windows APIs may make it less accessible or relevant for Linux users.
Recommendations
  • Add equivalent Bash/Azure CLI examples for creating resources and uploading files via FTP, using common Linux tools such as curl, lftp, or ftp.
  • Include instructions for installing and using Azure CLI, which is cross-platform, alongside PowerShell.
  • Reference Linux-native FTP tools and provide sample scripts for Linux/macOS environments.
  • Structure the documentation to present both Windows (PowerShell) and Linux (Bash/CLI) approaches, or clearly indicate platform-specific sections.
  • Avoid exclusive reliance on Windows APIs (like System.Net.FtpWebRequest) and mention cross-platform alternatives where possible.
GitHub Create Pull Request
← Previous Page 46 of 85 Next →