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 376-400 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-up.md
...docs/blob/main/articles/app-service/manage-scale-up.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing 'Azure App Service on Windows pricing', omitting any mention of Linux-based App Service plans, and providing no Linux-specific guidance or examples. All screenshots and feature comparisons are Windows-centric, and there is no discussion of Linux-specific scaling considerations or parity.
Recommendations
- Include references and links to Azure App Service on Linux pricing and documentation alongside Windows equivalents.
- Add explicit notes or sections describing any differences or additional steps when scaling Linux-based App Service plans.
- Provide screenshots and examples that show the experience for Linux-based App Service plans in the Azure portal.
- Ensure feature comparison tables and documentation cover both Windows and Linux App Service plans, highlighting any differences.
- Mention Linux-specific scaling considerations, such as supported features, quotas, or limitations, if any.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-nodejs.md
...cs/blob/main/articles/app-service/quickstart-nodejs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates some Windows bias, particularly in the Visual Studio Code (VS Code) deployment workflow. Windows-specific steps and tools (such as web.config, Application Insights, and resource group/App Service plan creation) are described in more detail and with more steps than their Linux counterparts. The Windows deployment instructions are more prominent and elaborate, and certain troubleshooting notes (e.g., about web.config) are only mentioned for Windows. There is also a reliance on Visual Studio Code, which is more common on Windows, and some steps reference Windows-centric patterns (e.g., 'right-click', 'Application Settings'). While Linux is supported and examples are present, parity in depth and troubleshooting is lacking. CLI and Portal instructions are more neutral, but the VS Code workflow leans Windows-first.
Recommendations
- Ensure that Linux deployment instructions are as detailed as Windows, including troubleshooting tips and common issues (e.g., what to do if the app doesn't start, or how to handle environment variables).
- Provide Linux-specific notes where Windows-specific notes are given (e.g., if web.config is needed for Windows, clarify what Linux expects instead, such as package.json start scripts).
- Balance the order and prominence of Linux and Windows instructionsβavoid always presenting Windows as the 'advanced' or default path.
- Where possible, use cross-platform terminology and avoid patterns that are only familiar to Windows users (e.g., 'right-click' could be 'context menu').
- Include explicit Linux troubleshooting sections, especially for common deployment errors.
- Mention and provide examples for Linux-native tools or workflows (e.g., using nano/vim for editing, or Linux file paths), not just VS Code.
- Clarify when steps are identical for both OSes, and when they diverge, to help users understand platform-specific requirements.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/reference-app-settings.md
...ob/main/articles/app-service/reference-app-settings.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation exhibits a Windows-first bias in several areas. Windows-specific paths, tools, and terminology (such as 'D:\home', 'w3wp.exe', 'Web Deploy/MSDeploy', and references to Windows Communication Foundation) are mentioned before or instead of their Linux equivalents. Many examples and default values are given only for Windows, with Linux alternatives either missing, less detailed, or presented after the Windows information. Some features are described primarily in terms of Windows tooling and behaviors, with Linux support noted as an exception or afterthought.
Recommendations
- Provide Linux and Windows examples side by side for environment variable values, file paths, and configuration steps.
- Ensure Linux-specific tools and behaviors (such as Oryx build automation, Linux file paths like '/home', and Linux container behaviors) are described with equal detail and prominence as Windows equivalents.
- Avoid using Windows terminology (e.g., 'D:\home', 'w3wp.exe', 'applicationHost.config') without also providing the Linux equivalent or clarifying when it is Windows-only.
- Where features or settings differ between Windows and Linux, clearly indicate the differences in a comparative table or callout, rather than describing Windows as the default and Linux as an exception.
- Add Linux-specific troubleshooting steps, examples, and references (e.g., for log file locations, deployment methods, and runtime behaviors) wherever Windows-specific guidance is given.
- Review and update references to Windows-only tools (such as MSDeploy, Web Deploy, and PowerShell scripts) to include Linux-friendly alternatives (such as SCP, rsync, Azure CLI, or bash scripts).
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing more detailed coverage and exclusive features for Windows-based apps. Several diagnostic tools and features (such as Proactive CPU Monitoring, Proactive Auto-Healing, and Navigator) are explicitly marked as 'Windows apps only', with no equivalent Linux guidance or alternatives provided. Linux support is mentioned in passing, but Linux-specific diagnostics are less prominent and lack detailed examples or instructions.
Recommendations
- Provide Linux-specific examples and walkthroughs for each diagnostic tool, especially where features differ between Windows and Linux.
- Clearly indicate feature parity or lack thereof for each tool, and suggest alternative troubleshooting steps for Linux where direct equivalents are unavailable.
- Include Linux-first or at least Linux-equal sections, not just Windows-first, and ensure Linux diagnostic categories are as detailed as Windows ones.
- Where a feature is Windows-only, offer a roadmap or workaround for Linux users, or link to relevant Linux troubleshooting documentation.
- Add screenshots and step-by-step guides for Linux diagnostics, similar to those provided for Windows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-local-cache.md
...blob/main/articles/app-service/overview-local-cache.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows-first bias. File paths and folder structures are described exclusively using Windows conventions (e.g., D:\home), and there is no mention of Linux equivalents or examples. Tools and features (such as Kudu/SCM) are referenced in a Windows-centric manner, and the only site extension suggested for disk usage is Azure Web Apps Disk Usage, which is tailored for Windows environments. There are no Linux command-line examples or references to Linux file system paths, and Linux/container scenarios are only mentioned as unsupported or as exceptions.
Recommendations
- Provide parallel Linux examples and file paths (e.g., /home/site/wwwroot) alongside Windows paths.
- Include Linux-specific instructions or notes where behaviors differ, especially for containerized and Linux App Service environments.
- Reference or suggest Linux-compatible tools for tasks such as disk usage analysis.
- Clarify which features and instructions apply to Windows, Linux, or both, ideally with a comparison table.
- When mentioning unsupported scenarios (e.g., Linux containers), provide links to alternative solutions or documentation for those environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-managed-identity.md
...main/articles/app-service/overview-managed-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing extensive Azure PowerShell examples and referencing PowerShell-specific modules and commands. PowerShell is a Windows-centric tool, and there are no equivalent Linux shell (bash) or cross-platform scripting examples. In several places, PowerShell instructions are given before or in more detail than Azure CLI, and there is no mention of Linux-specific tools or patterns. The documentation lacks explicit Linux shell (bash) or cross-platform scripting examples, which may disadvantage Linux users.
Recommendations
- Add bash (Linux shell) examples for all command-line operations, especially for token retrieval and identity management.
- Ensure Azure CLI examples are complete and presented before or alongside PowerShell examples, as Azure CLI is cross-platform.
- Avoid using PowerShell-specific syntax or modules in generic command-line examples; provide alternatives where possible.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows, and provide sample shell scripts for Linux users.
- Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide equivalent bash commands.
- Audit for any references to Windows-only tools or patterns and provide Linux/macOS equivalents.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Visual Studio and Windows-centric workflows, with all examples, screenshots, and instructions assuming the use of Visual Studio on Windows. There are no examples or guidance for Linux or cross-platform development environments, and all tooling (such as Server Explorer, Output window, and FTP via Windows Explorer) is Windows-specific. There is no mention of equivalent Linux tools or workflows, nor any parity for developers using VS Code, CLI, or non-Windows operating systems.
Recommendations
- Add equivalent instructions and screenshots for Linux and macOS users, including workflows using VS Code, Azure CLI, and cross-platform tools.
- Provide examples for accessing logs, remote debugging, and file management using the Azure CLI, Kudu console, or FTP clients available on Linux/macOS.
- Mention and link to cross-platform alternatives to Visual Studio features (e.g., VS Code Remote Debugging, Azure CLI log streaming, SFTP/FTP clients).
- Clearly indicate which features are Windows-only and provide guidance for users on other platforms.
- Reorganize sections to present cross-platform or CLI-based solutions before or alongside Windows/Visual Studio-specific instructions.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-private-endpoint.md
...main/articles/app-service/overview-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page shows mild Windows bias. While it states that private endpoints are available for both Windows and Linux apps, the related content and quickstart links list Azure PowerShell before CLI, and there is no explicit mention of Linux-specific tools or examples. The documentation references Kudu/scm endpoints and FTP, which are more commonly associated with Windows workflows. There are no Linux shell or scripting examples, and the only command-line example shown is Azure CLI, which is cross-platform, but PowerShell is given equal prominence in the quickstart links.
Recommendations
- Ensure that Linux-specific examples or notes are included where relevant, such as mentioning SSH access or Linux-based deployment tools.
- When listing quickstarts or scripts, list Azure CLI before PowerShell, as CLI is more cross-platform and widely used on Linux.
- Include explicit Linux shell (bash) examples alongside PowerShell where scripting is demonstrated.
- Clarify that Kudu/scm and FTP workflows are available for both Windows and Linux, or provide Linux-specific alternatives (e.g., SFTP, SSH).
- Add a section or note on how to perform private endpoint configuration and troubleshooting from a Linux environment.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation assumes a development environment based on GitHub Codespaces and .NET, which is cross-platform, but it implicitly favors Windows-centric workflows and tools. There are no explicit Linux or macOS terminal instructions, and the deployment and development steps (such as 'Open in Browser' and 'azd up') are described in a way that aligns more closely with Windows or Azure-centric environments. There is also a lack of explicit mention of Linux-native tools, shell commands, or alternative editors/terminals. The documentation does not provide parity for Linux users or acknowledge differences in workflow, such as using bash/zsh, local Linux development environments, or Linux package managers.
Recommendations
- Add explicit instructions for Linux and macOS users, including terminal commands and environment setup steps (e.g., using bash/zsh, dotnet CLI on Linux, and alternative editors).
- Clarify that the steps work cross-platform and provide notes on any OS-specific differences, such as file paths, environment variable syntax, or browser opening commands.
- Include examples of running and testing the app locally on Linux (e.g., using 'xdg-open' instead of 'Open in Browser', or noting how to access Swagger UI from a local browser).
- Mention Linux package managers and installation steps for .NET SDK and Azure Developer CLI on Linux.
- Ensure that all screenshots and UI references are either OS-neutral or include Linux/macOS variants where relevant.
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
Powershell Heavy
Summary
The documentation exhibits a mild Windows bias. Windows-specific instructions and examples are consistently presented before their Linux equivalents ("windows_first"). The use of Azure Cloud Shell and Azure CLI is mostly cross-platform, but there are references to Windows-specific tools and patterns, such as the use of the Azure portal's 'Advanced Tools' (Kudu), which is more commonly associated with Windows App Service. There is also a slight emphasis on Windows terminology and directory structures in the Windows section. However, both Windows and Linux instructions are provided, and there are no missing Linux examples.
Recommendations
- Alternate the order of Windows and Linux pivots in different sections to avoid always presenting Windows first.
- Where possible, use neutral terminology and avoid referencing tools or features that are exclusive or more common on Windows (e.g., Kudu/Advanced Tools) without noting their Linux equivalents.
- Ensure that all screenshots and walkthroughs are equally represented for both platforms, or provide platform-agnostic images.
- Explicitly mention any differences in behavior or tooling between Windows and Linux App Service, rather than assuming parity.
- Consider adding a summary table or section that highlights any platform-specific steps or caveats.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-asp-net-migration.md
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All migration tools and examples focus exclusively on migrating ASP.NET apps from Windows/IIS environments, with repeated references to Windows-specific tools (App Service Migration Assistant, PowerShell scripts) and no mention of Linux-based migration scenarios or tools. The documentation does not provide guidance or examples for migrating .NET apps hosted on Linux servers, nor does it mention Linux-native web servers (e.g., Apache, Nginx) or command-line tools (e.g., Bash scripts).
Recommendations
- Add examples and guidance for migrating .NET apps hosted on Linux servers (e.g., Apache, Nginx) to Azure App Service.
- Include Linux-specific migration tools or scripts, or clarify if such tools are not available.
- Provide parity in documentation by offering both Windows (PowerShell) and Linux (Bash, shell script) command-line examples for migration tasks.
- Mention any limitations or differences in migrating from Linux environments, and provide remediation steps or alternative approaches.
- Explicitly state the supported source environments (Windows, Linux) at the beginning of the documentation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates some Windows bias, particularly in the sections discussing configuration and process management. The only explicit tool mentioned for Node.js process management is PM2 on Linux, but the 'web.config' file and 'iisnode' settings are referenced without Linux equivalents or alternatives. The documentation refers to Windows-centric configuration patterns (web.config, iisnode) and does not provide parallel Linux-native examples or mention Linux-specific configuration files or process managers (other than PM2). There is also a tendency to mention Windows approaches first or exclusively, with Linux guidance appearing as an afterthought or in a limited context.
Recommendations
- For every mention of 'web.config' or 'iisnode', provide equivalent Linux-native configuration guidance (e.g., appsettings.json, environment variables, or nginx/apache configuration).
- When discussing auto-healing or process management, include Linux-native approaches (such as systemd, supervisord, or Azure-specific Linux features) alongside Windows methods.
- Ensure that examples and troubleshooting steps are provided for both Windows and Linux environments, and avoid assuming 'web.config' is universally applicable.
- When referencing tools or configuration files, explicitly state which OS/platform they apply to, and offer alternatives for the other platform.
- Consider providing side-by-side examples or a table comparing Windows and Linux approaches for common tasks (e.g., process management, configuration, diagnostics).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the 'Premium V3 availability' section, Windows SKU availability is listed before Linux, and the Linux command requires an extra flag. The automation section provides both Azure CLI and Azure PowerShell examples, but PowerShell is a Windows-centric tool. There are no explicit Linux shell (bash) script examples, and the PowerShell example is given equal prominence to the CLI example, despite CLI being cross-platform. Portal instructions and screenshots do not show OS-specific differences, but the overall pattern is to mention or demonstrate Windows-first or Windows-specific tools.
Recommendations
- Alternate the order of Windows and Linux instructions/examples, or present Linux first in some sections.
- Add bash shell script examples alongside Azure PowerShell, or clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Where possible, provide Linux-specific guidance or screenshots if there are UI or workflow differences.
- Consider including a table summarizing command differences for Windows and Linux users for clarity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by prioritizing Windows terminology, tools, and examples. PowerShell is presented as a primary automation tool, and while Azure CLI is cross-platform, there are no explicit Linux shell or scripting examples. Windows-specific features and limitations are discussed before Linux equivalents, and Linux automation or troubleshooting steps are not covered in parity with Windows.
Recommendations
- Provide Linux shell (bash) script examples alongside PowerShell for automation tasks.
- Ensure that Linux-specific instructions (e.g., for custom containers) are as detailed as Windows instructions.
- When listing features or limitations, present Linux and Windows information in parallel, not with Windows first.
- Include troubleshooting steps or common issues for Linux deployments, not just Windows.
- Clarify when instructions or features are platform-specific, and avoid assuming the reader is on Windows.
- Add explicit examples for Linux container deployments, since the Premium V4 tier supports them.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-asp-net-migration.md
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on migrating from Windows environments, specifically IIS servers, and make extensive reference to PowerShell scripts. There are no Linux or cross-platform migration scenarios, tools, or examples provided. The documentation assumes the source environment is Windows and does not mention Linux-based .NET hosting (e.g., Kestrel, Apache, Nginx) or provide guidance for those users.
Recommendations
- Include migration guidance and examples for .NET apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
- List Linux-compatible tools or scripts for discovery, assessment, and migration, or clearly state their absence and provide alternatives.
- Provide Bash or cross-platform CLI examples alongside PowerShell scripts.
- Mention Linux migration scenarios in tool descriptions and documentation tables, not just Windows/IIS.
- Clarify in the introduction that the current tools are Windows/IIS-focused and link to Linux migration resources if available.
- Add a section or FAQ addressing migration from Linux environments and any limitations or workarounds.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias, particularly in the 'Memory resources' and 'Node.js apps' sections. The use of 'web.config' and references to 'iisnode' are Windows/IIS-specific, with no equivalent Linux guidance or examples. While there is a brief mention of using PM2 for Node.js on Linux, the overall pattern is to present Windows-centric tools and configuration first or exclusively, with Linux alternatives either missing or less detailed.
Recommendations
- For 'Memory resources', provide Linux-specific configuration guidance (e.g., using environment variables or startup scripts) alongside or before 'web.config' for auto-healing.
- In the 'Node.js apps' section, add information about configuring Node.js apps on Linux App Service (e.g., using PM2, ecosystem.config.js, or other process managers) and clarify when 'iisnode' is relevant versus Linux-native approaches.
- Wherever Windows-specific tools or files (like 'web.config' or 'iisnode') are mentioned, add parallel Linux-native examples or note the differences in configuration between Windows and Linux App Service plans.
- Review the order of presentation to avoid always listing Windows/Windows tools first; consider starting with platform-agnostic or Linux examples where appropriate.
- Ensure troubleshooting and best practices sections include Linux-specific diagnostics and management options, not just those available via Windows/IIS.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias by listing Windows/Powershell options before Linux/CLI equivalents, providing detailed PowerShell examples, and referencing Windows-centric tools and navigation patterns. While Linux and Azure CLI are mentioned, Windows options are often presented first or more prominently, and there is heavier emphasis on PowerShell scripting.
Recommendations
- Present Linux and Windows options in parallel or alternate which is shown first, to avoid always prioritizing Windows.
- Provide equal depth and detail for Azure CLI (cross-platform) and Azure PowerShell examples.
- Where possible, use neutral language and screenshots that apply to both Windows and Linux users, or clearly indicate differences.
- Include explicit Linux navigation or shell instructions where relevant, not just Azure CLI commands.
- Ensure that all automation and scripting sections give equal weight to cross-platform tools (e.g., bash scripts, Azure CLI) as to PowerShell.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows terminology and tools (such as PowerShell) are presented prominently, and in some cases, before their Linux equivalents. While Azure CLI examples are provided (which are cross-platform), the PowerShell section is given equal prominence, and there are no explicit Linux shell (bash) script examples. The UI instructions and screenshots are based on the Azure Portal, which is platform-agnostic, but there is a lack of explicit Linux command-line or automation guidance. Additionally, the 'availability' section lists Windows before Linux, and there is no mention of Linux-specific considerations or tools outside of the Azure CLI flag.
Recommendations
- Add explicit Linux shell (bash) script examples alongside PowerShell for automation tasks.
- When listing availability or features, avoid presenting Windows before Linux unless there is a technical reason; consider grouping or alternating order.
- Clarify that Azure CLI commands work on both Windows and Linux, and provide sample bash scripts for common workflows.
- Include Linux-specific notes or troubleshooting tips where relevant, especially in automation and deployment sections.
- Ensure parity in example depth and detail between Windows (PowerShell) and Linux (bash/CLI) automation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-undelete.md
...blob/main/articles/app-service/app-service-undelete.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based command-line examples and referencing the Az PowerShell module throughout. There are no examples or instructions for Linux users (e.g., Bash, Azure CLI), and all automation steps are presented in a Windows-centric manner. The documentation does not mention or provide parity for Linux or cross-platform command-line tools, making it less accessible to users on non-Windows systems.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the PowerShell examples can be run on PowerShell Core on Linux/macOS, if applicable, or clarify any platform limitations.
- Provide Bash shell script examples where relevant, especially for common automation scenarios.
- Reorganize sections so that cross-platform solutions (such as Azure CLI) are presented before or alongside PowerShell examples, rather than only after.
- Include a table or section comparing PowerShell and Azure CLI commands for restoring deleted apps, to help users choose the tool that fits their environment.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-asp-net-migration.md
.../articles/app-service/app-service-asp-net-migration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All migration tools and examples focus exclusively on Windows environments, specifically IIS servers. Only Windows-based migration assistants and PowerShell scripts are mentioned, with no mention of Linux-based .NET hosting environments (such as Kestrel or Apache/Nginx), nor any Linux migration tools or examples. The documentation assumes the source environment is always Windows, omitting guidance for Linux users.
Recommendations
- Add equivalent migration guidance for .NET apps hosted on Linux servers (e.g., Kestrel, Apache, Nginx).
- Include Linux-specific migration tools or scripts, or clarify if such tools are not available.
- Provide Linux shell (bash) script examples alongside PowerShell examples.
- Mention and document migration paths for .NET Core/ASP.NET Core apps running on Linux.
- List Linux migration scenarios and any differences or limitations compared to Windows.
- Ensure that tool download links and documentation are available for both Windows and Linux environments, or explicitly state platform support.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-best-practices.md
...ain/articles/app-service/app-service-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates subtle Windows bias by referencing Windows-specific tools (such as web.config and iisnode) without providing equivalent Linux guidance or examples. While there is a brief mention of Linux in the Node.js section (regarding PM2), most configuration and troubleshooting advice (e.g., for auto-healing and Node.js settings) assumes a Windows-based environment or omits Linux-specific instructions. Linux-native configuration files and patterns are not discussed, and Windows-centric terminology appears first or exclusively.
Recommendations
- For features like auto-healing, provide Linux-specific configuration guidance (e.g., how to configure auto-healing for Linux-based App Service, or clarify if web.config is not applicable).
- When referencing iisnode or web.config for Node.js apps, include equivalent instructions for Linux-based App Service (such as using PM2, environment variables, or other Linux-native process managers and configuration files).
- Ensure that all examples and troubleshooting steps are provided for both Windows and Linux environments, or clearly indicate when a feature is platform-specific.
- Where Windows tools or patterns are mentioned, provide Linux equivalents either alongside or before the Windows examples to ensure parity and avoid Windows-first bias.
- Add explicit notes or links to Linux documentation where platform differences exist.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v3-tier.md
...s/app-service/app-service-configure-premium-v3-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias: Windows-specific terminology and tools (such as PowerShell) are mentioned before or more prominently than Linux equivalents. For example, the Azure PowerShell section is given equal prominence to Azure CLI, but there is no mention of Bash scripting or Linux shell automation. In the 'Premium V3 availability' section, the Windows SKU command is listed before the Linux SKU command. There are no explicit Linux shell or scripting examples, and the automation section does not mention Linux-specific tooling or patterns.
Recommendations
- Alternate the order of Windows and Linux examples (e.g., show Linux commands first in some sections).
- Include Bash or shell script examples alongside PowerShell, especially in automation sections.
- Explicitly mention Linux as a supported platform in automation and scripting contexts, not just in availability.
- Where possible, provide parity in screenshots and UI walkthroughs for both Windows and Linux users.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash or other shells, not just in Cloud Shell.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-key-vault-references.md
...ticles/app-service/app-service-key-vault-references.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for configuring Key Vault references, but consistently lists PowerShell examples immediately after CLI, with no mention of Linux-specific shell commands (e.g., Bash) or Linux-native tools. There are no explicit Linux command-line examples, and the only mention of Linux is in a note about networking configuration, not in practical usage or setup steps. This creates a subtle bias toward Windows and PowerShell users, and may leave Linux users without clear, platform-native guidance.
Recommendations
- Add Bash-specific examples alongside Azure CLI and PowerShell, especially for scripting identity assignment and app configuration.
- Explicitly mention that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Where PowerShell is shown, consider also showing equivalent Bash or shell script snippets for Linux users.
- Include troubleshooting steps or tips that are relevant to Linux environments (e.g., checking environment variables, file permissions).
- Clarify any platform-specific differences in behavior, especially for Linux-hosted apps, beyond the brief note about Flex Consumption plan networking.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-managed-certificate-changes-july-2025.md
...e/app-service-managed-certificate-changes-july-2025.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for advanced resource discovery and scenario analysis. While general guidance uses REST API and Azure CLI (which are cross-platform), all provided automation scripts for identifying impacted resources are PowerShell-based, with no Bash, shell, or Linux-native alternatives. The documentation refers to 'open PowerShell' and provides only PowerShell script download/run instructions, implicitly prioritizing Windows environments. There are no explicit Linux or macOS instructions or examples for these tasks.
Recommendations
- Provide equivalent Bash or shell scripts for all PowerShell scripts, or at least mention how Linux/macOS users can achieve the same results.
- When referencing downloadable scripts, clarify if they are cross-platform or provide alternatives for non-Windows users.
- Instruct users on how to use Azure CLI or REST API for resource discovery tasks where possible, as these are cross-platform.
- Avoid phrases like 'Open PowerShell' without also mentioning terminal or shell for Linux/macOS users.
- Explicitly state OS compatibility for any scripts or tools, and link to cross-platform documentation where available.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-configure-premium-v4-tier.md
...s/app-service/app-service-configure-premium-v4-tier.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows-related information and examples are often presented before Linux equivalents. PowerShell scripting is given equal prominence to Azure CLI, but no Linux shell (bash) scripting examples are provided. Portal instructions and screenshots are Windows-centric, and there is no mention of Linux-specific tools or workflows beyond the Azure CLI. The documentation does not provide parity in automation or troubleshooting examples for Linux users.
Recommendations
- Present Linux and Windows information in parallel, or alternate which comes first to avoid a 'windows_first' impression.
- Add bash shell scripting examples for automating tasks (e.g., using Azure CLI in bash), not just PowerShell.
- Include Linux-specific troubleshooting or deployment guidance where relevant.
- Clarify when instructions or screenshots are platform-agnostic or provide Linux-specific alternatives if there are differences.
- Where PowerShell is mentioned, explicitly note that Azure CLI commands work cross-platform and are recommended for Linux/macOS users.