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 1476-1500 of 2121 flagged pages
App Service Deploy Files ...zure-docs/blob/main/articles/app-service/deploy-zip.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates some Windows bias, notably in the following areas: (1) The Kudu ZIP deploy UI is only available for Windows, with Linux users directed to use alternatives. (2) Windows file paths (e.g., D:\home\site\wwwroot) are mentioned before Linux equivalents. (3) The use of Windows-centric tools and terminology (such as PowerShell and references to Web Deploy) is present, while Linux-specific tools or workflows are not highlighted or provided as first-class examples. (4) Some features (like the Kudu ZIP deploy UI) are not available for Linux, and Linux alternatives are mentioned only as a workaround, not with parity in explanation or examples.
Recommendations
  • Provide Linux-specific instructions and examples wherever a feature is Windows-only, including screenshots or step-by-step guides for Linux alternatives (e.g., FTP, ZIP deploy API).
  • Present Linux and Windows paths and workflows side-by-side, or in parallel, rather than listing Windows first.
  • Include Linux-native tools and commands (such as scp, rsync, or Linux shell scripts) where appropriate, especially in sections that currently only mention PowerShell or Windows tools.
  • Clearly indicate feature parity (or lack thereof) for each platform at the start of each section, and provide links to Linux/macOS-specific documentation if available.
  • Avoid using Windows-centric terminology (like 'Web Deploy') without also mentioning Linux alternatives and their usage.
GitHub Create Pull Request
App Service Certificates in App Service Environment ...icles/app-service/environment/overview-certificates.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias in the section describing per-app private client certificate configuration. This method is explicitly limited to Windows code apps, and all example commands (certificate inspection, creation, and export) use PowerShell, with no Linux/macOS equivalents or alternatives provided. The Kudu console and PowerShell are referenced as the only way to verify certificate installation, and Linux users are not given guidance for equivalent workflows. The main (recommended) environment-wide method is cross-platform, but the alternative per-app method is Windows-centric both in support and documentation.
Recommendations
  • Clearly state platform limitations at the start of the private client certificate section.
  • Provide Linux/macOS alternatives for certificate creation, export, and inspection (e.g., using OpenSSL and bash commands).
  • If possible, document how Linux apps can achieve similar outcomes, or clarify that no equivalent exists.
  • Add guidance for verifying certificate installation on Linux (if supported), or explicitly state that verification is only possible on Windows.
  • Ensure examples are presented for both platforms when features are cross-platform.
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
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation presents Windows examples and file types first, with explicit mention of Windows-specific tools (cmd, bat, exe, PowerShell) and their file extensions. Linux sections are shorter, only mentioning *.sh* scripts and lacking parity in examples for other runtimes (e.g., no mention of *.py*, *.js*, *.jar* in the main Linux code section). Windows sections provide more detail and variety, while Linux sections are minimal and less informative.
Recommendations
  • List Linux examples and supported file types with the same level of detail as Windows (e.g., include *.py*, *.js*, *.jar*, *.war* where applicable).
  • Provide Linux-specific tool references (e.g., Bash, Python, Node.js) and clarify runtime support for each.
  • Ensure examples for both platforms are equally comprehensive and presented in parallel structure.
  • Avoid presenting Windows sections first; consider grouping by file type or presenting both platforms side-by-side.
GitHub Create Pull Request
App Service Migrate Docker Compose to sidecars ...es/app-service/migrate-sidecar-multi-container-apps.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. The script-based migration is exclusively PowerShell-based, with no Bash or Linux shell alternative provided. PowerShell is listed as a prerequisite, and all scripting examples for automation use PowerShell syntax. Even in the manual migration, decoding the base64 Docker Compose file is shown only with a PowerShell command, with no Linux/macOS equivalent (e.g., using 'base64 -d'). Windows tools and patterns are mentioned first and exclusively in critical steps, making it harder for Linux/macOS users to follow the migration process.
Recommendations
  • Provide Bash or shell script alternatives for the migration script, or document how to run the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
  • Include Linux/macOS commands for base64 decoding (e.g., 'echo <base64value> | base64 -d').
  • List prerequisites for both Windows and Linux/macOS environments, including shell requirements and installation instructions.
  • Ensure that examples are given for both Windows (PowerShell) and Linux/macOS (Bash), or present them side-by-side.
  • Clarify whether the migration script can be run cross-platform, and if not, provide guidance or alternatives.
GitHub Create Pull Request
App Service Per-App Scaling for High-Density Hosting ...blob/main/articles/app-service/manage-scale-per-app.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions and code samples exclusively using Azure PowerShell cmdlets, which are most commonly used on Windows. There are no CLI (az), Bash, or Linux/macOS-specific examples for configuring per-app scaling, nor is there mention of cross-platform alternatives. This creates friction for Linux/macOS users who may prefer or require non-PowerShell workflows.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands shown.
  • Include Bash script samples for configuring per-app scaling.
  • Explicitly mention that PowerShell Core is cross-platform, if relevant, and provide installation guidance for non-Windows users.
  • Order examples so that CLI and ARM template approaches are presented before or alongside PowerShell.
  • Add a note clarifying that all steps can be performed from Linux/macOS using CLI or ARM templates.
GitHub Create Pull Request
App Service Monitor Azure App Service .../blob/main/articles/app-service/monitor-app-service.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page references Windows-centric tools and patterns, such as PowerShell, and mentions integration with Visual Studio before any Linux/macOS equivalents. Examples and instructions for querying Azure activity logs list PowerShell before CLI or REST API, and the Application Insights section highlights Visual Studio integration without mentioning cross-platform IDEs. There are no explicit Linux/macOS examples or tool recommendations, and the order of tool mentions tends to favor Windows-first approaches.
Recommendations
  • Provide Linux/macOS-specific examples and instructions alongside Windows/PowerShell ones, especially for querying logs and monitoring tasks.
  • Mention cross-platform IDEs (such as VS Code) and their integration with Application Insights, not just Visual Studio.
  • Ensure CLI and REST API examples are given equal prominence and are listed before or alongside PowerShell in instructions.
  • Add explicit references to Linux/macOS-compatible tools and workflows for monitoring and diagnostics.
GitHub Create Pull Request
App Service Managed Identities ...main/articles/app-service/overview-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell examples and references, which are primarily Windows-centric. PowerShell is presented as a first-class option alongside Azure CLI and ARM templates, and in some cases, PowerShell examples are more detailed or appear before Linux-friendly alternatives. There is also a notable focus on Azure PowerShell modules, which are less commonly used on Linux/macOS. However, Azure CLI and ARM template examples are present and generally cross-platform, mitigating the bias somewhat.
Recommendations
  • Clearly indicate which tools are cross-platform (e.g., Azure CLI, ARM templates) and recommend them for Linux/macOS users.
  • Where PowerShell is used, provide equivalent Bash or shell script examples for Linux/macOS users.
  • Avoid presenting PowerShell examples before CLI or ARM template examples, or alternate the order to avoid implicit prioritization.
  • Explicitly mention that Azure CLI works on Linux/macOS and link to installation guides for those platforms.
  • Add troubleshooting notes or caveats for PowerShell usage on non-Windows platforms, if relevant.
GitHub Create Pull Request
App Service Inbound/Outbound IP Addresses .../articles/app-service/overview-inbound-outbound-ips.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but PowerShell examples are shown alongside CLI without explicit mention of Linux shell alternatives. Outbound IPv6 support is noted as available only for Windows apps, with Linux users explicitly excluded from outbound IPv6 functionality. There are no Linux-specific troubleshooting or example sections, and PowerShell is referenced without Bash or Linux-native equivalents for some tasks.
Recommendations
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI as the primary example for parity.
  • Add Bash/Linux shell examples where appropriate, especially for tasks like querying IP addresses.
  • Explicitly state platform limitations (e.g., outbound IPv6 for Windows only) at the start of relevant sections and provide guidance or workarounds for Linux users.
  • Where PowerShell is used, add equivalent Bash or shell script examples for Linux/macOS users.
  • Consider reordering examples to show CLI/Bash first, then PowerShell, to avoid implicit Windows-first bias.
GitHub Create Pull Request
App Service Overview of Azure App Service .../azure-docs/blob/main/articles/app-service/overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias, especially in the Managed Instance section, which exclusively highlights Windows-specific features (COM, registry, MSI, drive mapping, PowerShell scripts, RDP) and tools. Windows workloads and tools are described in detail, while Linux and container support are only mentioned as unsupported in this context, with no equivalent Linux examples or tooling discussed. Windows tools (PowerShell, RDP) are mentioned before or instead of Linux alternatives, and there is a lack of Linux-specific guidance for similar scenarios.
Recommendations
  • Provide Linux and container-specific examples and tooling where possible, especially in sections discussing deployment, scripting, and diagnostics.
  • Include parity tables or feature comparisons to clarify which features are available on Linux and how to achieve similar outcomes.
  • Mention Linux command-line tools (e.g., Bash, shell scripts) alongside PowerShell, and provide examples for both platforms.
  • Clarify which features are Windows-only and suggest Linux alternatives or workarounds.
  • Ensure that documentation sections do not assume Windows as the default platform, and present Linux options equally.
GitHub Create Pull Request
App Service Routine Maintenance, Restarts, and Downtime ...n/articles/app-service/routine-maintenance-downtime.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed explanations and references for Windows-specific features (such as IIS Application Initialization Module and .NET Core stdout logging) before mentioning Linux equivalents, and by omitting Linux-specific examples or tools in several sections. Linux mechanisms are referenced briefly or as an afterthought, with less detail and no direct links to implementation guides. This creates friction for Linux users seeking parity in guidance and troubleshooting.
Recommendations
  • Provide equal detail and step-by-step examples for Linux features, such as WEBSITE_WARMUP_PATH, including links to relevant documentation.
  • Include Linux-first or side-by-side examples for warm-up, health check, auto-heal, and logging strategies.
  • Reference Linux-native tools and patterns (e.g., Nginx, Apache, stdout/stderr logging, systemd) where appropriate.
  • Ensure troubleshooting and testing sections include Linux-specific scenarios and recommendations.
  • Balance the order of presentation so Linux and Windows approaches are described together, not with Windows first.
GitHub Create Pull Request
App Service Quickstart: Deploy an ASP.NET web app ...lob/main/articles/app-service/quickstart-dotnetcore.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
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 first and in greatest detail, with extensive screenshots and step-by-step instructions. PowerShell instructions are included, but are explicitly recommended only for Windows hosting, and the PowerShell deployment workflow uses Windows-specific commands (e.g., Compress-Archive with backslashes). The .NET Framework 4.8 workflow is Windows-only. While cross-platform options (VS Code, CLI, Azure Portal) are provided, Windows tools and patterns are often mentioned first or exclusively, and Linux-specific guidance is sometimes relegated to notes or omitted (e.g., PowerShell section tells Linux users to use CLI instead). There are no explicit Linux shell (bash) examples for zipping/publishing, and some instructions (like file paths) use Windows conventions.
Recommendations
  • Present cross-platform (CLI, VS Code, Azure Portal) instructions before or alongside Windows/Visual Studio workflows.
  • Provide explicit Linux/macOS shell examples for steps like zipping/publishing (e.g., use 'zip' command with forward slashes).
  • Clarify when instructions are Windows-only and offer Linux/macOS alternatives in the same section (not just as notes).
  • Include screenshots or references for Linux/macOS environments where applicable.
  • Avoid recommending PowerShell as the default unless the workflow is truly Windows-specific; otherwise, highlight CLI as the cross-platform default.
  • For .NET 10.0, emphasize its cross-platform nature and show parity in deployment steps for Linux/macOS users.
GitHub Create Pull Request
App Service Create a scheduled WebJob with prebuilt samples ...s/blob/main/articles/app-service/quickstart-webjobs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows examples and tools before Linux equivalents. The Windows tab lists a broader set of scripting languages (CMD, Batch, PowerShell, F#, etc.) and appears first, while the Linux tab is more limited. Windows-specific tools and patterns (CMD, Batch, PowerShell) are highlighted, with no Linux shell script equivalents for those languages. The overall structure and language selection suggest a Windows-first approach.
Recommendations
  • Present Linux and Windows tabs in parallel or alternate their order to avoid implicit prioritization.
  • Expand Linux examples to include equivalents for scripting languages available on Windows (e.g., provide shell script alternatives for PowerShell, Batch, and F# where possible).
  • Add a note clarifying platform-specific limitations and offering guidance for Linux users seeking similar functionality.
  • Ensure that all language samples are available for both platforms where technically feasible.
GitHub Create Pull Request
App Service Kudu service overview ...-docs/blob/main/articles/app-service/resources-kudu.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references Windows-specific tools and features (IIS diagnostic dumps, IIS processes, Windows deployment webhooks) without mentioning Linux equivalents or clarifying their applicability to Linux-based App Service plans. There are no examples or guidance for Linux users, and the features described may not be available or relevant for Linux-hosted apps.
Recommendations
  • Clarify which Kudu features are available for Linux-based App Service plans and which are Windows-only.
  • Provide examples and instructions for using Kudu with Linux-based apps, including accessing logs, managing processes, and deployment options.
  • Mention Linux-specific diagnostic tools or alternatives where IIS features are referenced.
  • Add a section comparing feature parity between Windows and Linux App Service environments.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses storage by using managed identities | Azure ...cles/app-service/scenario-secure-app-access-storage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides installation instructions for required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console (PowerShell). However, the Visual Studio/PowerShell example is given equal prominence to the cross-platform .NET CLI, and there is no explicit mention of Linux/macOS alternatives for package management or development environments. The instructions assume Visual Studio and PowerShell, which are primarily Windows tools, and do not reference Linux-native editors or package management workflows.
Recommendations
  • Clarify that the .NET Core CLI commands work on Windows, Linux, and macOS, and recommend them as the primary cross-platform method.
  • Move the .NET Core CLI instructions before the Visual Studio/PowerShell instructions to emphasize cross-platform compatibility.
  • Add explicit instructions for Linux/macOS users, such as using VS Code or JetBrains Rider, and mention that Visual Studio is Windows-only.
  • Remove or de-emphasize PowerShell/Package Manager Console instructions unless there is a Windows-specific scenario.
  • Include troubleshooting notes for Linux/macOS users if there are known issues or differences.
GitHub Create Pull Request
App Service Enable Diagnostic Logging ...n/articles/app-service/troubleshoot-diagnostic-logs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Logging features such as web server logging, detailed error messages, and failed request tracing are described exclusively for Windows, with no Linux equivalents or alternatives mentioned. Windows-specific tools (e.g., Log Parser) and file paths are referenced, and Windows instructions are often presented before Linux ones. Linux logging capabilities are described more briefly, and some features are explicitly unavailable or unsupported for Linux, with no suggested workarounds.
Recommendations
  • Clearly indicate which logging features are Windows-only and provide Linux alternatives or workarounds where possible.
  • Expand Linux sections to describe equivalent logging and troubleshooting workflows, including how to access and interpret logs.
  • Include Linux-first or side-by-side examples for all major logging scenarios, not just application logging.
  • Reference Linux-native tools for log analysis (e.g., grep, less, jq) alongside Windows tools.
  • Add troubleshooting and diagnostic guidance for Linux apps, including container-specific logging patterns.
  • Where features are unavailable on Linux, suggest best practices or third-party solutions.
GitHub Create Pull Request
App Service Troubleshoot Performance Degradation ...es/app-service/troubleshoot-performance-degradation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-specific tools (IIS, Procdump, PowerShell), provides links and examples for Windows App Service features (such as .NET Profiler for Windows), and mentions Windows-centric troubleshooting patterns (Kudu console with PowerShell/DOS commands, SysInternals). Linux equivalents (e.g., Bash, Linux diagnostics, Linux-specific logging) are not mentioned, and there are no examples or guidance for Linux-based App Service environments.
Recommendations
  • Add explicit guidance and examples for Linux-based App Service environments, including how to collect diagnostics, enable logging, and troubleshoot performance.
  • Mention Linux-compatible tools and commands (e.g., Bash, Linux log paths, Linux process dump utilities) alongside Windows tools.
  • Provide parity in documentation for enabling profilers and diagnostics on Linux App Service plans.
  • Clarify when instructions or features are Windows-only, and link to Linux-specific alternatives where available.
  • Include PowerShell and Bash/Azure CLI examples side-by-side for management tasks.
GitHub Create Pull Request
App Service Tutorial: Build and Run a Custom Image in Azure App Service ...main/articles/app-service/tutorial-custom-container.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias in the 'container-windows' pivot. Windows examples are presented first, with detailed, step-by-step instructions using Windows-specific tools (Visual Studio, Windows Explorer, PowerShell scripts). There is heavy reliance on Windows-only patterns (installing fonts via Windows Explorer, using InstallFont.ps1, and Visual Studio workflows). Linux equivalents for these steps (e.g., installing fonts, building containers with non-Windows tools) are absent in the Windows section, and the Linux pivot is presented after the Windows content. The Linux section is more CLI-focused and cross-platform, but the overall structure and depth of the Windows section may create friction for Linux/macOS users seeking parity.
Recommendations
  • Provide Linux/macOS equivalents for all major steps in the Windows section, including font installation, Docker image creation, and deployment workflows.
  • Avoid assuming Visual Studio or Windows Explorer as the default tools; offer alternatives such as VS Code, command-line instructions, or cross-platform editors.
  • Include PowerShell script alternatives using Bash or shell scripts for Linux/macOS users.
  • Present Windows and Linux pivots with equal prominence and detail, ensuring that both workflows are equally discoverable and complete.
  • Explicitly note platform-specific requirements and offer guidance for users on other platforms.
GitHub Create Pull Request
App Service Fix HTTP 502 and HTTP 503 Errors ...articles/app-service/troubleshoot-http-502-http-503.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell for app management, mentioning DOS commands in the Kudu console, and highlighting Windows-centric tools like Sysinternals ProcDump. There are no explicit Linux or macOS command-line examples, nor are Linux-native troubleshooting tools or shell commands (e.g., Bash) mentioned. Windows tools and patterns are referenced before any Linux equivalents (if any), and Linux users are left to infer how to adapt instructions.
Recommendations
  • Add equivalent Linux/macOS command-line examples for app management (e.g., Azure CLI, Bash commands).
  • Mention that the Kudu console supports Bash and provide sample Bash commands for Linux users.
  • Reference cross-platform tools for memory dumps (e.g., dotnet-dump, gcore) alongside ProcDump.
  • Clarify which instructions or tools are platform-specific and provide alternatives for Linux/macOS.
  • Ensure troubleshooting steps and screenshots are not exclusively Windows-centric.
GitHub Create Pull Request
App Service Tutorial: Connect a web app to SQL Database on behalf of the user ...utorial-connect-app-access-sql-database-as-user-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. While Azure CLI (cross-platform) is used for most automation, critical database management steps reference Windows-centric tools like SQL Server Management Studio (SSMS) and sqlcmd, with no mention of Linux/macOS alternatives. Visual Studio (Windows-only) is featured for publishing and debugging, with Linux/macOS options (Git Bash, VS Code) mentioned but not prioritized. No explicit Linux/macOS database tooling examples are provided.
Recommendations
  • Include explicit instructions and examples for connecting to Azure SQL using cross-platform tools (e.g., Azure Data Studio, sqlcmd on Linux/macOS, or VS Code SQL extensions).
  • When referencing SSMS, also mention Azure Data Studio or other cross-platform database clients.
  • Provide Linux/macOS command-line examples for database user management (e.g., using sqlcmd installed via Homebrew or apt).
  • Show publishing/deployment steps using cross-platform tools (e.g., Azure CLI, VS Code) before or alongside Visual Studio instructions.
  • Clarify which steps are OS-agnostic and which require Windows, offering alternatives where possible.
GitHub Create Pull Request
App Service Tutorial: Access Azure databases with managed identity ...les/app-service/tutorial-connect-msi-azure-database.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, particularly in the developer environment setup section. Visual Studio for Windows is described first and in more detail, while Visual Studio for Mac is noted as lacking integration and requires a workaround. Visual Studio Code and CLI options are presented, but Windows-specific tools and patterns (Visual Studio for Windows, Azure PowerShell) are mentioned before their cross-platform or Linux equivalents. Azure PowerShell is included as a development option, but Linux-native shells or tools are not highlighted. There are no explicit Linux/macOS command-line examples beyond Azure CLI, and the overall flow assumes familiarity with Windows-centric development environments.
Recommendations
  • Present cross-platform or Linux/macOS options before or alongside Windows-specific instructions, especially in the 'Set up your dev environment' section.
  • Provide explicit Linux/macOS examples for signing in and configuring development environments, including common shells (bash/zsh) and editors (e.g., JetBrains Rider, VS Code on Linux).
  • Clarify that Azure CLI and Visual Studio Code are fully cross-platform, and highlight their parity for Linux/macOS users.
  • Include troubleshooting or notes for common Linux/macOS issues (e.g., permissions, environment variables).
  • Avoid assuming Visual Studio for Windows as the default IDE; balance coverage with cross-platform tools.
GitHub Create Pull Request
App Service Build a scheduled WebJob using your preferred language ...ocs/blob/main/articles/app-service/tutorial-webjobs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The .NET section of the documentation demonstrates a moderate Windows bias: Windows build and packaging commands are presented first, and Windows-specific instructions (e.g., .exe, win-x64) are more prominent. Linux instructions are present but sometimes appear as secondary tabs or require extra steps (e.g., creating run.sh). The references to supported file types and CRON expressions link to pages with 'windowscode' tabs, which may reinforce a Windows-centric view. Other language pivots (Python, Node, Java, PHP) focus on Linux, but the .NET pivot is notably Windows-first.
Recommendations
  • Present Linux and Windows instructions side-by-side, or default to the user's platform if detectable.
  • Ensure Linux build and packaging steps are as detailed and prominent as Windows steps.
  • Avoid referencing supporting documentation with 'windowscode' tabs only; provide Linux/macOS equivalents.
  • Clarify any differences in behavior or requirements between Windows and Linux WebJobs up front.
  • Include troubleshooting tips for Linux users, especially around executable permissions and script entry points.
GitHub Create Pull Request
App Service Tutorial for event-driven background processing with the WebJobs SDK ...b/main/articles/app-service/webjobs-sdk-get-started.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows and Visual Studio workflows. All code/project creation steps are described using Visual Studio 2022 UI, and all package installation commands use PowerShell (Package Manager Console), with no mention of Linux/macOS alternatives (e.g., dotnet CLI, VS Code, or cross-platform editors). There are no instructions for Linux/macOS users on how to create, build, or run the project, nor any guidance for installing dependencies outside Visual Studio. The documentation assumes the user is on Windows and using Visual Studio, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent instructions for Linux/macOS users, including how to create and manage .NET projects using the dotnet CLI.
  • Include package installation commands using 'dotnet add package' instead of (or in addition to) PowerShell/Package Manager Console.
  • Provide guidance for using VS Code or other cross-platform editors.
  • Explicitly state platform requirements and alternatives in the prerequisites section.
  • Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented together or Linux/macOS instructions are not omitted.
  • Clarify how to run and debug the project on Linux/macOS (e.g., using 'dotnet run').
GitHub Create Pull Request
App Service Quickstart: Use Terraform to configure an Azure App Service Environment v3 ...articles/app-service/environment/creation-terraform.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but Azure PowerShell is given equal prominence as Azure CLI, despite PowerShell being primarily a Windows tool. There are no Linux-specific shell examples (e.g., Bash), and PowerShell usage may be less familiar or available on Linux platforms. The order of presentation (CLI first, then PowerShell) is reasonable, but the inclusion of PowerShell as a primary tab may signal Windows bias.
Recommendations
  • Ensure all command-line examples work seamlessly on Linux/macOS (e.g., Bash shell).
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash shell examples or notes for Linux users, especially for variable assignment and command syntax.
  • If PowerShell is included, note its cross-platform availability but clarify its historical Windows focus.
  • Review other sections for implicit assumptions about Windows environments (e.g., file paths, tool installation instructions).
GitHub Create Pull Request
App Service [Portal](#tab/azure-portal) ...torial-dotnet-storage-managed-identity/introduction.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is consistently listed before Azure CLI in all code example sections. This ordering may suggest a preference for Windows environments. There are no Linux-specific tools, shell, or OS-specific instructions, and PowerShell is not as commonly used on Linux as on Windows.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first, as it is cross-platform and more common on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary Linux-specific notes (e.g., line continuation differences, shell requirements).
  • Where possible, include bash shell examples or highlight any OS-specific considerations.
  • If referencing Visual Studio (a Windows-first IDE), also mention cross-platform alternatives (e.g., VS Code) for Linux users.
GitHub Create Pull Request
App Service Configure Premium V3 Tier ...s/app-service/app-service-configure-premium-v3-tier.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but PowerShell (a Windows-centric tool) is given its own dedicated section after the CLI. There are no Linux shell-specific examples (e.g., Bash scripts), and the portal instructions do not mention platform differences. The CLI examples do distinguish between Windows and Linux SKUs, but overall, Windows tools (PowerShell) are highlighted, and Linux-native scripting is absent.
Recommendations
  • Add Bash shell script examples for Linux users alongside Azure CLI and PowerShell.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Include notes or sections for Linux-specific automation patterns (e.g., using shell scripts, cron jobs).
  • Ensure that PowerShell is not presented as the only or primary automation tool, and balance with Linux-native approaches.
  • Explicitly mention platform parity in portal instructions if any differences exist.
GitHub Create Pull Request
← Previous Page 60 of 85 Next →