App Service
806
Total Pages
669
Linux-Friendly Pages
137
Pages with Bias
17.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
247 issues found
Showing 101-125 of 247 flagged pages
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows examples and tools before Linux equivalents. The Windows tab includes more scripting options (CMD, Batch, PowerShell, F#) that are specific to Windows, while the Linux tab only lists cross-platform languages. Windows-specific tools and patterns (CMD, Batch, PowerShell) are highlighted, and the order of presentation prioritizes Windows. There is no mention of Linux-specific scripting languages (e.g., shell variants beyond Bash) or Linux-native tools.
Recommendations
- Present Linux and Windows options with equal prominence, possibly listing Linux first or side-by-side.
- Include Linux-native scripting examples (e.g., Perl, Ruby, or other common Linux scripting languages) if relevant.
- Add explanations for why certain scripting languages/tools are only available on Windows, and suggest Linux alternatives.
- Ensure that instructions and samples for both platforms are equally detailed and comprehensive.
- Avoid listing Windows-specific tools (CMD, Batch, PowerShell) without Linux equivalents or alternatives.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by providing installation instructions using Visual Studio's Package Manager Console (PowerShell) and referencing Windows-specific tooling before mentioning cross-platform alternatives. There is no explicit mention of Linux or macOS environments, nor are there examples using Linux-native tools or instructions for non-Windows users.
Recommendations
- Add explicit instructions for installing NuGet packages on Linux/macOS, such as using the .NET CLI (which is cross-platform) and clarify that it works on all platforms.
- Reorder installation instructions to present the .NET Core command-line (dotnet CLI) method first, as it is platform-agnostic, before mentioning Windows-specific Package Manager Console.
- Include a note or section for Linux/macOS users, highlighting any platform-specific considerations (e.g., how to open a terminal, install .NET SDK, etc.).
- Avoid referencing Visual Studio or Windows-only tools without also mentioning cross-platform alternatives.
- Ensure that all examples and instructions are clearly marked as cross-platform where applicable, and provide parity for Linux/macOS users.
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 →
Detected Bias Types
Windows First
Windows Examples
Missing Linux Example
Summary
The documentation provides both Linux and Windows template samples, but Windows examples are generally listed before Linux equivalents in several sections. There are more Windows-specific scenarios (including Windows containers and database connections) than Linux ones, and some sections group Linux examples separately, suggesting Windows as the default. Some connected resource examples are only shown for Windows, with Linux equivalents either missing or listed separately.
Recommendations
- Present Linux and Windows examples together, in parallel, rather than grouping Windows as default and Linux as a special case.
- Ensure every Windows scenario (e.g., database connections, containers) has a Linux equivalent, or explicitly state if not supported.
- Alternate the order of examples, or use neutral headings (e.g., 'App Service plan and basic app (Linux/Windows)').
- Add more Linux-focused samples, such as Linux container deployments, to match Windows parity.
- Review and update connected resource examples to ensure both OS platforms are equally represented.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its instructions for installing NuGet packages: it lists the Visual Studio Package Manager Console (PowerShell-based, Windows-only) before mentioning the .NET Core CLI, and provides PowerShell install commands without equivalent Linux/macOS shell examples. There is no explicit mention of Linux or cross-platform development environments, nor are Linux-specific instructions or screenshots provided.
Recommendations
- Provide explicit Linux/macOS instructions for installing NuGet packages, such as using the .NET CLI in bash/zsh.
- List cross-platform (CLI) instructions before Windows-specific (Visual Studio/PowerShell) instructions.
- Clarify that the .NET CLI commands work on Windows, Linux, and macOS, and include example shell commands for Linux/macOS environments.
- Avoid referencing Windows-only tools (like Package Manager Console) without mentioning alternatives for other platforms.
- Include notes or screenshots for Linux/macOS environments where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/terraform-secure-backend-frontend.md
...p-service/scripts/terraform-secure-backend-frontend.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using Windows-based App Service resources (azurerm_windows_web_app, os_type: Windows) in the Terraform examples. There are no examples or mentions of Linux-based web apps (azurerm_linux_web_app, os_type: Linux), nor any guidance on deploying Linux workloads. The documentation also references Windows-specific service plans and omits Linux equivalents, which may mislead users into thinking only Windows is supported or recommended.
Recommendations
- Include parallel examples using azurerm_linux_web_app and os_type: Linux to demonstrate Linux parity.
- Mention that both Windows and Linux App Service plans are supported and provide guidance for choosing between them.
- Add notes or sections highlighting differences and considerations for Linux-based deployments (e.g., app settings, runtime support).
- Ensure that any referenced tools, scripts, or commands are cross-platform or provide Linux alternatives where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scripts/template-deploy-private-endpoint.md
...pp-service/scripts/template-deploy-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by exclusively providing a PowerShell example for resource cleanup, without mentioning or providing equivalent commands for Linux users (such as Azure CLI or Bash). The use of PowerShell cmdlets and lack of cross-platform instructions may hinder Linux users from following the guide seamlessly.
Recommendations
- Include Azure CLI examples alongside PowerShell for resource group deletion (e.g., 'az group delete --name <your resource group name>').
- Explicitly mention that both Windows and Linux users can use the Azure Portal for deployment, and provide CLI/Bash alternatives where possible.
- Add notes or sections clarifying cross-platform compatibility and provide links to relevant Linux documentation.
- Review other steps for implicit Windows assumptions and ensure parity in instructions for Linux/macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/troubleshoot-http-502-http-503.md
...articles/app-service/troubleshoot-http-502-http-503.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary CLI tool for managing Azure resources, mentioning DOS commands in the Kudu console, and suggesting the use of Windows-specific tools like ProcDump. There are no examples or mentions of Linux shell equivalents, nor are Linux troubleshooting tools or commands provided. Windows-centric patterns and terminology appear before or instead of Linux alternatives.
Recommendations
- Include Linux shell (bash/sh) command examples for managing Azure resources, such as using Azure CLI in bash.
- Mention Linux-compatible diagnostic tools (e.g., gcore, strace, lsof) alongside ProcDump for memory dumps and troubleshooting.
- Clarify that the Kudu console supports both PowerShell and bash, and provide examples for both environments.
- Avoid using Windows/DOS terminology exclusively; provide parity with Linux commands and workflows.
- Add explicit instructions or links for troubleshooting on Linux-based App Service environments.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. It references Windows-specific tools (such as IIS logs, Procdump from SysInternals, and PowerShell), and links to resources with 'Windows' in the title. Examples and instructions for Linux-based App Service environments are missing, and Windows-centric terminology and tools are mentioned first or exclusively. There is no mention of Linux equivalents for diagnostics, logging, or troubleshooting, nor are Bash or Linux command-line examples provided.
Recommendations
- Add explicit instructions and examples for Linux-based App Service environments, including how to access logs, enable diagnostics, and troubleshoot performance.
- Include Bash or Linux shell command examples alongside PowerShell commands.
- Reference Linux-native tools (such as strace, lsof, top, or gdb) for diagnostics and memory dumps, and explain how to use them in App Service on Linux.
- Clarify which features and tools are available on Windows vs. Linux App Service plans, and provide links to Linux-specific documentation where appropriate.
- Avoid using Windows-centric terminology (e.g., IIS, web.config) without noting Linux alternatives (e.g., Apache/Nginx, app settings).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-auth-aad.md
...cs/blob/main/articles/app-service/tutorial-auth-aad.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows instructions and examples are presented before Linux equivalents in several sections, and some tooling references (such as Azure portal navigation and 'Advanced Tools') are more familiar to Windows users. While Linux-specific pivots are present, they are sometimes less detailed or appear after Windows instructions. There are no PowerShell-specific examples, but the overall flow and screenshots are more Windows-centric.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which platform appears first in each section.
- Ensure screenshots and portal navigation steps are equally clear for Linux users, possibly including Linux-specific screenshots where UI differs.
- Explicitly mention any differences in tooling or behavior between Windows and Linux App Service plans.
- Where possible, provide CLI-only instructions that work identically on both platforms, reducing reliance on portal steps.
- Review all examples for parity in detail and clarity between Windows and Linux pivots.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While the main workflow uses Azure CLI (cross-platform), several sections reference Windows-centric tools (SQL Server Management Studio, Visual Studio, and Integrated Windows authentication) without mentioning Linux alternatives or giving parity to Linux workflows. The publishing instructions and local debugging guidance are focused on Visual Studio and Git Bash, omitting Linux-native editors and deployment methods. There are no explicit Linux or macOS examples for connecting to SQL Database, debugging, or publishing, and Windows tools are mentioned first or exclusively in some cases.
Recommendations
- Include examples for connecting to Azure SQL Database using Linux-native tools such as Azure Data Studio, sqlcmd on Linux, or other cross-platform clients.
- Add instructions for publishing code using Linux editors (e.g., VS Code on Linux, JetBrains Rider) and deployment via Azure CLI or Git from Linux/macOS terminals.
- When referencing SQL Server Management Studio (SSMS), also mention Azure Data Studio as a cross-platform alternative.
- Provide local debugging guidance for Linux and macOS environments, including how to obtain and use access tokens outside of Windows.
- Avoid mentioning Windows authentication patterns unless directly relevant, and clarify differences for Linux users.
- Ensure screenshots and step-by-step instructions are not Windows-specific, or provide Linux/macOS equivalents where appropriate.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows development environments, specifically Visual Studio, and provides instructions and examples exclusively for Windows users. There are no references to Linux development workflows, tools, or deployment patterns. All UI instructions, screenshots, and project templates are based on Visual Studio for Windows, and there is no mention of cross-platform alternatives or command-line approaches suitable for Linux users.
Recommendations
- Add instructions for developing and deploying WebJobs using cross-platform tools such as VS Code, the Azure CLI, or GitHub Actions.
- Include Linux-specific examples for creating, configuring, and deploying WebJobs, such as using the dotnet CLI and zip deployment.
- Reference alternative editors and workflows (e.g., JetBrains Rider, VS Code) that work on Linux and macOS.
- Provide guidance for managing WebJobs from Linux environments, including file structure and deployment steps.
- Ensure parity in screenshots and step-by-step guides for non-Windows platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-custom-container.md
...in/articles/app-service/quickstart-custom-container.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Windows-specific pivots (Visual Studio, PowerShell, CLI) before Linux equivalents, and by providing dedicated sections for Windows tools (PowerShell, Visual Studio) without clear Linux parity (e.g., Bash, Linux CLI). The presence of multiple Windows pivots and tools suggests a prioritization of Windows workflows and technologies.
Recommendations
- Ensure Linux pivots (e.g., VS Code, Azure Portal, CLI) are presented before or alongside Windows pivots to avoid perceived prioritization.
- Add or highlight Linux-native tools and workflows (e.g., Bash scripts, Linux CLI examples) where Windows tools (PowerShell, Visual Studio) are featured.
- Balance the number of Windows and Linux pivots/examples to provide equal coverage for both platforms.
- Explicitly mention Linux alternatives whenever a Windows-specific tool or pattern is introduced.
- Review included files to ensure Linux instructions are as detailed and prominent as Windows instructions.
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 →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page displays a Windows bias, particularly in the 'Managed Instance on App Service (preview)' section, which focuses exclusively on Windows-specific features (COM, registry, MSI, drive mapping, PowerShell, RDP) and tools. Windows tools and patterns (PowerShell, RDP, registry, MSI) are mentioned without Linux equivalents or alternatives. While the general overview claims support for both Windows and Linux, concrete examples and advanced features are Windows-centric, and Linux/container support is only mentioned as 'not supported' in the Managed Instance context. There are no Linux-specific examples or advanced scenarios provided.
Recommendations
- Provide Linux-specific advanced scenarios or features, especially in sections where Windows features are highlighted (e.g., Managed Instance).
- Include Linux command-line examples (e.g., Bash scripts) alongside PowerShell examples where relevant.
- Mention Linux tools and patterns (such as systemd, cron, or Linux package managers) when discussing automation or configuration.
- Clarify feature parity and limitations for Linux and containers, and link to Linux/container-specific documentation for advanced use cases.
- Ensure that when listing command-line tools, Linux-native tools (e.g., Azure CLI in Bash) are given equal prominence to Azure PowerShell.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a Windows bias by presenting Visual Studio for Windows instructions before macOS and VS Code, emphasizing Windows-integrated authentication, and providing explicit Azure PowerShell examples. Windows-specific tools and patterns (Visual Studio for Windows, Azure PowerShell) are described in greater detail, while Linux-native or cross-platform alternatives (such as Linux IDEs or shell environments) are not mentioned. The macOS and VS Code sections rely on Azure CLI, but Linux is not referenced directly as a development environment, nor are Linux-specific tools or workflows discussed.
Recommendations
- Add explicit instructions for setting up development environments on Linux, including common IDEs (e.g., JetBrains Rider, VS Code on Linux, or command-line workflows).
- Provide parity in authentication setup examples for Linux users, such as using Azure CLI and environment variables.
- Mention Linux as a supported platform in the prerequisites and environment setup sections.
- Include troubleshooting tips and code samples relevant to Linux environments (e.g., bash shell, Linux file paths, package managers).
- Ensure that cross-platform tools (Azure CLI, VS Code) are presented before or alongside Windows-specific tools to avoid Windows-first ordering.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several Windows-centric biases. Windows-specific details, examples, and tooling (such as PowerShell and Windows Server image recommendations) are often presented first or exclusively, while Linux equivalents are sometimes less detailed or omitted. PowerShell commands are frequently included alongside Bash, and Windows-specific concepts (like IIS, .NET Framework, and C:\home) receive more thorough coverage. Some advanced configuration and troubleshooting sections are richer for Windows than for Linux, and certain Linux instructions (e.g., SSH setup) are relegated to later sections.
Recommendations
- Ensure Linux examples and instructions are presented with equal prominence and detail as Windows, including parent image recommendations and troubleshooting steps.
- Where PowerShell commands are provided, always include equivalent Bash or shell commands for Linux users, and consider listing Bash first in Linux-focused sections.
- Expand Linux-specific guidance for advanced topics such as persistent storage, diagnostic logging, and environment variable management to match Windows coverage.
- Avoid Windows-first ordering in general sections; use neutral or parallel presentation for cross-platform features.
- Clarify differences in default behaviors (e.g., persistent storage enabled/disabled) in a comparative table or summary for quick reference.
- Add more Linux-specific troubleshooting tips and references, similar to the depth given for Windows containers.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed, code-level examples for accessing certificates in Windows apps and containers (including C# and Java), but offers minimal or no equivalent code examples for Linux apps outside of .NET. Linux coverage is limited to C# file-based loading, with other languages (Node.js, PHP, Python, Java) referred to external documentation. Windows certificate store usage is described in detail, while Linux approaches are less thoroughly covered. Windows-specific tools and patterns (certificate store, thumbprint usage) are emphasized first.
Recommendations
- Add explicit code examples for loading certificates in Linux containers and apps for popular languages such as Node.js, Python, Java, and PHP.
- Provide Linux-focused .NET examples earlier or alongside Windows examples, not only in later sections.
- Include a brief explanation of Linux certificate handling and best practices, similar to the Windows certificate store discussion.
- Where possible, avoid referencing only Windows certificate store APIs and provide cross-platform alternatives or guidance.
- Reorder sections or use tabs to present Windows and Linux approaches in parallel, reducing the 'Windows-first' impression.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across Windows and Linux platforms. However, there is a noticeable Windows bias: Windows-specific paths (e.g., D:\home), tools (e.g., msbuild, Web Deploy/MSDeploy), and configuration patterns (e.g., applicationHost.config, IIS, machineKey) are often mentioned first or exclusively. Windows terminology and examples appear before Linux equivalents, and some sections (such as build automation and logging) focus heavily on Windows-native tools and settings, with Linux alternatives referenced later or less prominently. Linux-specific settings are present, but Windows-centric information dominates in order and detail.
Recommendations
- Ensure Linux examples and paths (e.g., /home) are given equal prominence alongside Windows examples, especially in introductory tables and explanations.
- Where Windows tools (e.g., msbuild, Web Deploy/MSDeploy) are referenced, provide Linux alternatives or clarify their applicability.
- Reorder sections or tables so Linux and Windows information is presented in parallel, rather than Windows-first.
- Expand Linux-specific guidance (e.g., Oryx build automation, logging, deployment) to match the detail provided for Windows.
- Add explicit notes when a setting or feature is Windows-only, and provide Linux equivalents or workarounds where possible.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux, but there is a consistent pattern of Windows-specific details, tools, and paths being mentioned first or exclusively in several sections. Some examples and descriptions use Windows paths (e.g., D:\home), reference Windows tools (e.g., msbuild, Web Deploy/MSDeploy), or focus on IIS and Windows-specific behaviors. In some cases, Linux equivalents are mentioned, but often as an afterthought or with less detail. There are also sections where only Windows tools or patterns are described, and Linux users must infer or seek out external documentation.
Recommendations
- Ensure that all examples and environment variable descriptions provide both Windows and Linux paths and behaviors where applicable, with equal prominence.
- When referencing Windows tools (e.g., msbuild, Web Deploy), also mention Linux equivalents (e.g., Oryx, Kudu for Linux) and provide links or brief explanations.
- Avoid defaulting to Windows paths or terminology (e.g., D:\home) in general sections; instead, show both (e.g., D:\home (Windows), /home (Linux)).
- Where tabs are used for Windows and Linux (e.g., Kudu vs. Oryx), ensure both are equally detailed and easy to find.
- Add Linux/macOS-specific examples and troubleshooting notes where only Windows is currently covered.
- Review for sections where Windows-only features are described without a Linux note, and clarify platform applicability.
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides comprehensive coverage of environment variables and app settings for Azure App Service, but there is a notable Windows bias in several areas. Windows-specific paths (e.g., D:\home), tools (e.g., Web Deploy/MSDeploy), and configuration files (e.g., applicationHost.config, Web.config) are frequently referenced, often before or instead of Linux equivalents. Some sections, such as build automation and Java/.NET settings, provide more detail for Windows (Kudu, MSDeploy, Jetty/Tomcat on Windows) than for Linux (Oryx, Tomcat on Linux). Linux-specific instructions and examples are present but less detailed and sometimes appear after Windows content. There are also several environment variables and features that are only described for Windows, with Linux coverage being less explicit or omitted.
Recommendations
- For every Windows-specific path or example (e.g., D:\home), provide the Linux equivalent (/home) alongside or first.
- When referencing Windows tools like Web Deploy or MSDeploy, explicitly mention Linux deployment alternatives and provide links or examples.
- Ensure that Linux-specific features (e.g., Oryx build automation, Tomcat on Linux) are described with equal detail and clarity as their Windows counterparts.
- Where variables or behaviors differ between Windows and Linux, clearly indicate the differences in tables or callouts.
- Add more Linux/macOS command-line examples and troubleshooting steps where only Windows/PowerShell examples are given.
- Review sections that reference configuration files (e.g., Web.config, applicationHost.config) to clarify their applicability and provide Linux/container equivalents if available.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation displays a moderate Windows bias. Windows concepts and tools (Azure PowerShell, Windows-specific SKUs) are often presented first or exclusively, while Linux equivalents are less emphasized or missing. For example, PowerShell automation is shown, but no Bash/Linux shell or scripting example is provided. The 'Automate with scripts' section gives both Azure CLI and PowerShell, but not Bash or other Linux-native scripting. The portal instructions are generic, but the CLI examples for Linux are less prominent. The documentation does note Linux availability, but the overall pattern favors Windows-first presentation and tooling.
Recommendations
- Add explicit Bash or Linux shell script examples for automation, not just Azure CLI and PowerShell.
- When listing SKUs or commands, present Linux and Windows examples with equal prominence, or clarify differences in a parallel structure.
- Include Linux-native scripting (e.g., Bash) in the 'Automate with scripts' section.
- Where PowerShell is mentioned, also mention Bash or other Linux scripting options.
- Consider a table or side-by-side comparison for Windows and Linux steps where they differ.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a moderate Windows bias. Windows-specific information and tools (such as Azure PowerShell) are mentioned before Linux equivalents, and PowerShell scripting is given equal prominence to Azure CLI, despite CLI being more cross-platform. The 'Automate with scripts' section provides both Azure CLI and PowerShell examples, but PowerShell is a Windows-centric tool. In the 'Premium v4 availability' section, the Windows SKU example is shown before Linux. However, Linux-specific instructions are present where relevant, and Azure CLI examples are provided.
Recommendations
- Present Linux and Windows examples in parallel or with equal prominence, rather than listing Windows first.
- Clarify that Azure CLI is cross-platform and recommend it as the default automation tool for Linux/macOS users.
- Where PowerShell is shown, explicitly mention that it is primarily for Windows users and provide Bash or shell script equivalents for Linux/macOS.
- In the 'Premium v4 availability' section, consider listing Linux and Windows commands together or in a neutral order.
- Add explicit notes or links for Linux/macOS users where UI or tool differences may exist.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides a generally cross-platform overview but introduces notable Windows bias in the Managed Instance section, which is Windows-only and highlights Windows-specific features and tools (e.g., COM, registry, MSI, PowerShell, RDP) without Linux equivalents or alternatives. Windows tools (PowerShell, RDP) are mentioned exclusively, and Linux support is only referenced as 'not supported' without further guidance or parity.
Recommendations
- Clearly separate Windows-only features (like Managed Instance) and provide equivalent Linux/container guidance or alternatives where possible.
- Include Linux-focused examples or scenarios, especially in sections discussing command-line tools and deployment patterns.
- When mentioning Windows tools (e.g., PowerShell, RDP), also mention Linux alternatives (e.g., Bash scripts, SSH) where applicable.
- Provide links or references to Linux/container documentation for users seeking those options.
- In decision guides, offer more detail on Linux/container use cases, not just as a negative ('not supported'), but with positive guidance.
App Service
Quickstart: Deploy an ASP.NET web app
...lob/main/articles/app-service/quickstart-dotnetcore.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Visual Studio (Windows-only) is presented as the primary development environment, with detailed step-by-step instructions and screenshots. PowerShell is recommended for Windows hosting and receives its own section, while Linux equivalents are referenced but not given equal prominence or detail. Some CLI and VS Code instructions are cross-platform, but Windows tools and workflows are generally described first and in greater depth. There are also cases where Linux users are redirected to other tools rather than provided direct instructions.
Recommendations
- Ensure that Linux-specific instructions are provided with equal detail and screenshots, especially for publishing and deployment steps.
- Present cross-platform tools (such as Azure CLI and VS Code) before Windows-only tools in the documentation flow.
- Avoid recommending PowerShell as the default for Windows hosting; instead, clarify parity and provide equivalent Bash/Linux shell examples.
- Include explicit instructions and examples for Linux users in all major sections, not just references to other documentation.
- Balance screenshots and walkthroughs between Windows and Linux environments.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in its examples and configuration patterns. Most code samples and configuration instructions reference Windows-specific paths (e.g., 'c:\data\import'), and there is a lack of explicit Linux/macOS equivalents or guidance. The documentation does not mention Linux/macOS-specific tooling, environment variables, or file system paths, nor does it provide parity examples for non-Windows platforms. This may create friction for developers working on Linux/macOS, especially when configuring file bindings or running WebJobs locally.
Recommendations
- Provide Linux/macOS equivalents for file system paths in all examples (e.g., '/home/user/data/import').
- Explicitly mention that environment variables and configuration files work cross-platform, and note any platform-specific caveats.
- Include notes or sections on running and developing WebJobs on Linux/macOS, including any required dependencies or differences in behavior.
- Ensure that all examples and instructions are platform-neutral or provide alternatives for each major OS.
- Reference cross-platform tools (such as Azure CLI) where relevant, and avoid assuming Visual Studio or Windows-only tooling.
App Service
Discover .NET Apps to Azure App Service
...cles/app-service/app-service-migration-discover-net.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation focuses exclusively on discovering ASP.NET web apps hosted on IIS servers, which are Windows-specific. There is no mention of Linux-based hosting environments (e.g., Apache, Nginx), nor are there examples or guidance for discovering .NET apps on Linux or macOS. All tooling and discovery flows assume a Windows/IIS context, creating friction for users with Linux-based .NET deployments.
Recommendations
- Add guidance and examples for discovering .NET web apps hosted on Linux (e.g., using Apache, Nginx, or Kestrel).
- Clarify whether Azure Migrate supports Linux-based .NET app discovery and, if so, provide instructions.
- Include references to Linux-compatible tools or scripts for discovery, if available.
- Explicitly state platform limitations if discovery is Windows-only, to set expectations for Linux/macOS users.