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 1876-1900 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-create-arc-environment.md
.../articles/app-service/manage-create-arc-environment.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for most steps, but PowerShell is given equal prominence to Bash, and in some cases, appears before or alongside Bash rather than being secondary. There is a notable focus on Azure CLI and PowerShell scripting, which are more common in Windows environments. There are no Linux-specific tools, patterns, or troubleshooting tips, and the documentation does not address Linux-specific nuances (such as differences in base64 encoding flags or shell environment setup). The use of Azure Cloud Shell (which is Linux-based) is mentioned, but the examples and structure do not prioritize Linux-native workflows or highlight Linux-specific considerations.
Recommendations
- Prioritize Bash examples before PowerShell in all code tabs and sections, as Bash is the default shell for most Linux environments.
- Add Linux-specific troubleshooting notes (e.g., differences in base64 command flags, file permissions, or environment variable syntax).
- Explicitly mention that all commands are tested in Linux environments and note any differences for Windows users as secondary.
- Provide a section or callout for users running native Linux (outside Azure Cloud Shell), including any prerequisites or environment setup steps unique to Linux.
- Where PowerShell is shown, clarify that it is optional and primarily for Windows users, and avoid presenting it as equally standard as Bash.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-authentication-authorization.md
...s/app-service/overview-authentication-authorization.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by describing the feature architecture for Windows (IIS module) before Linux/containers, and by referencing Windows-specific technologies (IIS modules) without providing equivalent technical details or links for Linux. However, the page does not provide command-line examples that are Windows-specific (e.g., PowerShell), and the configuration examples use cross-platform Azure CLI (az rest), which is not Windows-specific. There are no missing Linux examples, but the technical depth and terminology favor Windows.
Recommendations
- Present Linux and Windows architectures in parallel, or start with a neutral overview before platform-specific details.
- Provide equivalent technical details and links for Linux/container deployments (e.g., link to Ambassador pattern documentation, describe the Linux authentication module in more depth).
- Avoid using Windows-specific terminology (such as 'IIS module') without also explaining the Linux/container equivalent.
- Where possible, include diagrams or tables that compare Windows and Linux behaviors side by side.
- Ensure that all configuration and troubleshooting instructions are clearly cross-platform, and explicitly mention any differences or limitations for Linux/container environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/overview-inbound-outbound-ips.md
.../articles/app-service/overview-inbound-outbound-ips.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for finding outbound IP addresses, but the PowerShell examples are always presented immediately after the CLI examples, and no explicit Linux shell or Bash scripting examples are given. The CLI examples are cross-platform, but the presence of PowerShell (a Windows-centric tool, though now available on Linux) may suggest a slight Windows bias. There are no exclusive references to Windows-only tools, but the documentation does not explicitly mention Linux or provide Linux-specific guidance or troubleshooting.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
- Consider providing Bash shell scripting examples or notes for Linux users, especially for common tasks like parsing output.
- If PowerShell examples are included, mention that PowerShell Core is available on Linux and macOS, or provide equivalent Bash examples.
- Explicitly state that all commands shown (unless otherwise noted) work on both Windows and Linux environments.
- Add troubleshooting notes or links for common issues Linux users might encounter (e.g., permissions, path differences).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/quickstart-java.md
...docs/blob/main/articles/app-service/quickstart-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page uses a pivot structure to separate instructions for different Java stacks (Tomcat, Java SE, JBoss). However, for Java SE and JBoss, only Windows-based quickstart includes are referenced, while only Tomcat has a Linux-based quickstart. This results in missing Linux examples for Java SE and JBoss, and Windows instructions are prioritized for those stacks.
Recommendations
- Provide Linux-based quickstart documentation for Java SE and JBoss stacks, similar to the Tomcat example.
- Ensure that for each Java stack, both Windows and Linux deployment instructions are available and equally discoverable.
- Review included files to confirm parity in content depth and clarity between Windows and Linux instructions.
- Consider a unified structure where both OS options are presented side-by-side or with clear pivots for each stack.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-terraform.md
...cs/blob/main/articles/app-service/samples-terraform.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page lists Terraform samples for Azure App Service, but the examples provided focus exclusively on Windows-based web apps and containers. There are no Linux-based app or container examples, and the scripts specifically mention 'Windows' in their titles and descriptions. This demonstrates both a 'windows_first' and 'missing_linux_example' bias.
Recommendations
- Add equivalent Terraform samples for creating Linux web apps and Linux container apps on Azure App Service.
- Ensure that for every Windows-specific example, a Linux counterpart is provided and clearly labeled.
- Consider reordering or grouping examples so that Linux and Windows samples are presented with equal prominence.
- Explicitly mention in the documentation that both Windows and Linux are supported, and provide guidance for both platforms.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/resources-kudu.md
...-docs/blob/main/articles/app-service/resources-kudu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page references Windows-specific tools and patterns (such as IIS diagnostic dumps, IIS processes, and deployment webhooks for Windows apps) without mentioning Linux equivalents or clarifying Linux support. There are no examples or features highlighted for Linux-based App Service environments, and the documentation does not provide parity in describing Linux-specific Kudu features or usage.
Recommendations
- Include information about Kudu features and diagnostics available for Linux-based App Service apps, such as how to access logs, manage processes, or run commands in the Kudu console for Linux.
- Clarify which features (e.g., IIS diagnostic dumps, IIS process management, deployment webhooks) are Windows-only and provide Linux alternatives or note their absence.
- Add explicit examples or walkthroughs for both Windows and Linux App Service environments to ensure users on both platforms understand how to use Kudu.
- Mention Linux-specific deployment patterns or troubleshooting steps where relevant, to balance the Windows focus.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/samples-bicep.md
...e-docs/blob/main/articles/app-service/samples-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation presents both Linux and Windows examples for basic app deployment, but in several cases, Windows-specific scenarios (such as Windows container apps and Windows with MySQL) are included without equivalent Linux examples. Additionally, Windows examples are sometimes listed before Linux ones, and there is no parity in the types of connected resource scenarios offered for Linux (e.g., no 'App with MySQL on Linux'). There are no command-line or tooling examples, so no PowerShell or Windows tool bias is present.
Recommendations
- Add Linux equivalents for all Windows-specific scenarios (e.g., 'App with MySQL on Linux', 'App Service plan and Linux container app').
- Ensure that for each scenario (basic app, connected resources, containers), both Linux and Windows examples are provided.
- Alternate the order of Linux and Windows examples or group them together to avoid implicit prioritization.
- Review connected resource scenarios to ensure Linux parity (e.g., CosmosDB is Linux-only, MySQL is Windows-only; provide both combinations).
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes the use of GitHub Codespaces and .NET tooling, but does not provide any Linux-specific instructions or examples. All terminal commands and deployment steps are generic, but there is an implicit bias toward Windows environments (e.g., App Service, .NET, and Azure Developer CLI), and there are no explicit Linux shell or deployment examples. There are no references to Linux-specific tools, nor are there instructions for running or deploying the app on a local Linux machine or using Linux-native workflows.
Recommendations
- Add explicit instructions or notes for running the tutorial on Linux, including any differences in environment setup, terminal commands, or file paths.
- Provide Linux shell command equivalents where relevant (e.g., bash instead of PowerShell, if any OS-specific commands are used).
- Include a section or callout for users developing on Linux or macOS, highlighting any differences or confirming that the steps are cross-platform.
- Mention and provide examples for deploying from a local Linux environment, not just Codespaces or Azure CLI.
- If using .NET, clarify that the SDK and CLI are cross-platform and provide links to Linux installation guides.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section about clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is mentioned, with no equivalent instructions for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps involving system commands (such as clearing DNS cache), include equivalent instructions for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Explicitly mention that the instructions apply to all platforms, or provide platform-specific tabs or notes where commands differ.
- Review other troubleshooting or command-line examples to ensure parity across Windows, Linux, and macOS environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-webjobs.md
...ocs/blob/main/articles/app-service/tutorial-webjobs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a mild Windows bias by referencing 'windowscode' tabs in links for supported file types and CRON expressions across all language pivots, regardless of whether the example is Linux-based. The links such as [supported file types](webjobs-create.md?tabs=windowscode#acceptablefiles) and [CRON expressions](webjobs-create.md?tabs=windowscode#ncrontab-expressions) default to Windows-specific documentation, even when the rest of the instructions and code samples are Linux-oriented (using Bash scripts and Linux paths). There are no explicit PowerShell or Windows command-line examples, but the persistent use of 'windowscode' in documentation links may cause confusion or suggest Windows is the primary or preferred environment.
Recommendations
- Update all links to supported file types and CRON expressions to use a neutral or Linux-appropriate tab (e.g., 'linuxcode' or a generic tab) when the language pivot is for Linux-based stacks.
- Ensure that referenced documentation and screenshots reflect the OS context of the current language pivot (e.g., show Linux file structures and tools for Python, Node, PHP, Java).
- Where possible, clarify in the documentation that the instructions and scripts are for Linux environments, and provide Windows equivalents only if relevant.
- Consider adding a short note explaining any OS-specific differences in WebJob packaging or execution, especially if users may be deploying to both Windows and Linux App Service plans.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Path Pattern
Summary
The documentation provides parity for both Windows and Linux App Service apps, mentioning both platforms in backup content tables and referencing persistent storage for custom containers. However, there are subtle Windows biases: Windows path patterns (e.g., `%HOME%`, `D:\home\site\wwwroot`) are shown first or exclusively in some file instructions, and the use of Kudu DebugConsole (which is more familiar to Windows users) is referenced without mentioning Linux alternatives. FTP upload instructions use Windows-style paths. PowerShell is mentioned as a scripting option, but Linux shell scripting is not referenced. Overall, Linux users can complete all tasks, but Windows patterns are prioritized or assumed in some examples.
Recommendations
- Provide Linux path examples (e.g., `/home/site/wwwroot`) alongside Windows paths in file instructions and upload steps.
- Clarify that Kudu DebugConsole is available for both Windows and Linux App Service apps, and mention Linux-native tools (e.g., SCP, SFTP) for file upload.
- When referencing scripting, mention Bash or shell scripting as alternatives to PowerShell.
- In tables and instructions, list Windows and Linux content equally (not Windows first).
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is focused on gateway-required virtual network integration, which is explicitly stated to only work for Windows plans. However, troubleshooting and connectivity examples (such as Test-NetConnection in PowerShell) are provided only for Windows, with no Linux/macOS equivalents. The use of Windows tools and commands is presented first and exclusively, and Linux users are not given guidance for comparable tasks. This creates friction for Linux users who may need to troubleshoot or understand related concepts, even though the feature itself is Windows-only.
Recommendations
- Clarify early and prominently that all operational and troubleshooting steps are Windows-specific due to the feature limitation.
- Where troubleshooting steps are relevant to general networking (e.g., testing connectivity from a VM), provide Linux/macOS equivalents (such as 'nc', 'telnet', or 'curl' for TCP connectivity tests).
- Add a note in troubleshooting sections that Linux users should use their platform's tools, and provide example commands.
- Ensure that any generic networking advice is platform-neutral or includes both Windows and Linux/macOS examples.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance using zone pivots, but Windows-specific examples, tools, and terminology (such as PowerShell, Windows Server base images, and IIS/ASP.NET) are often presented first or in greater detail. PowerShell commands are included alongside Bash/Azure CLI, and Windows-specific tooling (like Kudu and references to C:\home) appear throughout. Linux equivalents are present but sometimes less detailed or appear after Windows instructions.
Recommendations
- Ensure Linux-specific examples and explanations are as detailed and prominent as Windows ones.
- Where possible, present Linux and Windows instructions side-by-side, rather than Windows-first.
- Expand Linux troubleshooting and diagnostic sections to match Windows depth (e.g., Kudu, SSH, logs).
- Review for any Windows terminology or tooling that could be replaced with cross-platform alternatives.
- Clarify persistent storage paths for Linux (avoid referencing C:\home in Linux pivots).
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Path Bias
Summary
The documentation is generally cross-platform and uses Azure CLI as the primary scripting example, which is available on all major OSes. However, there are several instances where Windows conventions, paths, and tools are mentioned first or exclusively, such as using Windows-style environment variables (%HOME%), Windows directory paths (D:\home\site\wwwroot), and references to Kudu DebugConsole and FTP uploads without explicit Linux/macOS equivalents. There are also minor references to Windows-specific features (e.g., MySQL in-app for Windows), but these are called out as such. Linux paths and conventions are mentioned, but often after Windows, and sometimes only in explanatory tables.
Recommendations
- When referencing file paths, provide both Windows and Linux/macOS equivalents (e.g., D:\home\site\wwwroot and /home/site/wwwroot).
- When mentioning environment variables like %HOME%, also mention $HOME for Linux/macOS.
- In sections about uploading files (e.g., _backup.filter), suggest cross-platform tools (such as SCP, SFTP, or Azure CLI az webapp create-remote-connection) alongside FTP and Kudu DebugConsole.
- When showing examples or screenshots, alternate between Windows and Linux views, or clarify that the instructions apply to both.
- Explicitly state that the Azure CLI commands work on all platforms, and provide troubleshooting tips for common Linux/macOS issues if applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is structured to cover both Windows and Linux containers, with clear pivots for each. However, there are several sections where Windows-specific information, examples, and tools (such as PowerShell) are presented first or in greater detail. PowerShell examples are consistently provided alongside Bash/Azure CLI, and Windows parent images and tools are discussed before Linux equivalents. Some Windows-specific features (like IIS, .NET Framework, and machine key injection) are covered in dedicated pivots, but Linux parity is generally maintained. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Where possible, alternate the order of Windows and Linux pivots or present Linux examples first in some sections.
- Ensure that Linux-specific parent image recommendations and cached images are listed with equal prominence as Windows images.
- For generic configuration tasks (environment variables, persistent storage, etc.), clarify Linux-specific paths and behaviors before or alongside Windows details.
- Consider providing Bash/Azure CLI examples before PowerShell, or at least in parallel, to avoid implicit Windows-first bias.
- Review pivoted content for completeness and parity, ensuring Linux pivots are as detailed as Windows pivots.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC permissions, but PowerShell is presented as a first-class option throughout. References to Windows tools (IIS, Certreq.exe) for certificate export are given, and the FAQ links to both Azure CLI and PowerShell scripts, but PowerShell is mentioned first. The certificate export section mentions OpenSSL for Linux/macOS, but also references Windows-specific tools and links to Windows documentation. Overall, Windows tools and patterns are mentioned alongside Linux equivalents, but Windows options are often presented first or more prominently.
Recommendations
- Ensure Linux/macOS tools (OpenSSL, Azure CLI) are mentioned before or alongside Windows tools in all relevant sections.
- Provide explicit Linux/macOS instructions and links for certificate export and management, not just OpenSSL commands.
- In automation sections and FAQs, list Azure CLI examples before PowerShell, or clarify parity between the two.
- Where Windows-specific tools are referenced (IIS, Certreq.exe), add equivalent Linux/macOS guidance or clarify when Windows-only steps are required.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Pathing
Summary
The documentation is generally cross-platform, with Azure Portal and Azure CLI instructions (CLI being cross-platform). However, there are several instances where Windows conventions, tools, or paths are mentioned first or exclusively, and PowerShell is referenced alongside CLI for automation. Linux equivalents are present but sometimes secondary. There are minor references to Windows paths and tools (e.g., D:\home, %HOME%, Kudu DebugConsole, FTP) without always clarifying Linux alternatives. PowerShell is mentioned as an automation option, but no Bash or shell script samples are provided. Overall, Linux/macOS users can complete all tasks, but some friction exists due to Windows-first conventions.
Recommendations
- When referencing file paths (e.g., %HOME%, D:\home), also mention Linux equivalents (e.g., /home/site/wwwroot).
- When describing how to upload files (e.g., via FTP or Kudu DebugConsole), clarify that these tools are available for both Windows and Linux App Service plans, and mention SFTP or SCP as alternatives.
- When listing automation options, provide Bash/shell script examples or explicitly state that Azure CLI commands work on all platforms.
- If referencing PowerShell, also reference Bash or shell scripting for parity.
- In tables or lists where both Windows and Linux are supported, avoid listing Windows first unless there is a technical reason.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Patterns
Summary
The documentation is generally cross-platform, but there are subtle Windows biases. Windows file paths and environment variables (e.g., `%HOME%`, `D:\home\site\wwwroot`) are shown first or exclusively in some examples. The use of Kudu DebugConsole and references to FTP upload methods are described with Windows-style paths. The documentation mentions both Azure CLI and PowerShell for automation, but PowerShell is listed second. Linux equivalents are present (e.g., `/home` directory), but Windows patterns are more prominent.
Recommendations
- Where file paths are shown (e.g., `_backup.filter` location), provide both Windows and Linux examples, such as `D:\home\site\wwwroot\` and `/home/site/wwwroot/`.
- When referencing environment variables, clarify both `%HOME%` (Windows) and `$HOME` (Linux).
- In sections describing access via Kudu or FTP, mention Linux/macOS tools and path conventions.
- Ensure that CLI examples are equally applicable and clarify any OS-specific nuances.
- Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is structured to cover both Windows and Linux custom containers in Azure App Service, with clear pivots for each platform. However, in several cross-platform sections, Windows/PowerShell examples are consistently presented before Linux/Bash equivalents, and some advanced configuration and diagnostic sections are more detailed for Windows. PowerShell commands are provided alongside Bash, but often Windows terminology and tools (e.g., C:\home, IIS, .NET Framework) are mentioned first or in more depth. Linux parity is generally good, but the ordering and emphasis may create friction for Linux users.
Recommendations
- In cross-platform sections, alternate the order of Windows and Linux examples, or present Linux examples first where appropriate.
- Ensure that all advanced configuration and troubleshooting topics have equally detailed Linux sections, especially for diagnostics and persistent storage.
- Where possible, avoid Windows-centric terminology in general sections (e.g., refer to '/home' before 'C:\home' in shared storage explanations).
- Add more Linux-specific troubleshooting and best practices, matching the depth provided for Windows.
- Consider using tabs or collapsible sections for command-line examples, so users can easily select their platform.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is focused on a feature (gateway-required virtual network integration) that is explicitly Windows-only, as stated in the prerequisites. However, the troubleshooting and example commands (e.g., Test-NetConnection, netstat -aon) are Windows/PowerShell-centric, and there are no equivalent Linux/macOS commands or guidance. The use of Windows tools is presented without alternatives, and PowerShell/Windows commands are shown exclusively.
Recommendations
- Clearly state at the top that this feature is Windows-only, which is already done, but consider making this even more prominent.
- In troubleshooting sections, provide equivalent Linux/macOS commands (e.g., use 'nc' or 'telnet' for TCP connectivity, 'ss' or 'netstat' for port checks) where possible, since users may be diagnosing from non-Windows VMs.
- When referencing tools like 'tcpping' or 'Test-NetConnection', mention cross-platform alternatives or note that these are Windows-specific.
- If any steps can be performed from Linux/macOS (e.g., updating routes, checking connectivity from a Linux VM), provide those examples as well.
App Service
Migrate from gateway-based to regional virtual network integration
.../app-service/migrate-gateway-based-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides example commands for Azure portal, Azure CLI, and Azure PowerShell in all procedural sections. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented alongside CLI and portal examples. In most cases, PowerShell examples are given equal prominence to CLI, but sometimes appear before CLI. There are no Linux-specific tools or shell examples (e.g., Bash, scripting), and no explicit mention of Linux/macOS user experience. However, the documentation does not rely solely on Windows tools, and all critical tasks can be completed using Azure CLI, which is cross-platform.
Recommendations
- Ensure Azure CLI examples are always presented before Azure PowerShell examples, as CLI is cross-platform.
- Explicitly state that Azure CLI works on Linux/macOS and is recommended for non-Windows users.
- Consider adding Bash shell scripting examples for common migration tasks, or clarify that Azure CLI commands can be run in Bash.
- If PowerShell is included, clarify its cross-platform availability (PowerShell Core) or note any limitations for Linux/macOS users.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for RBAC role assignment, but PowerShell is featured equally and sometimes before Linux-native tools. Windows-specific tools (IIS, Certreq.exe) are referenced for certificate export, while Linux tools (OpenSSL) are also included. However, Windows export instructions are more prominent and linked, and PowerShell is given as a primary automation example alongside CLI. The FAQ and automation sections mention PowerShell and CLI, but do not reference Bash or Linux-specific scripting. Overall, Linux users can complete all tasks, but Windows tools and patterns are mentioned first or equally, creating minor friction.
Recommendations
- Include Bash scripting examples for certificate automation alongside PowerShell and CLI.
- Provide explicit instructions for certificate export from macOS/Linux (e.g., using Keychain or OpenSSL), not just Windows tools.
- When listing automation options, mention Azure CLI and Bash first, then PowerShell, to reduce Windows-first bias.
- Add links to Linux/macOS certificate management documentation where Windows tools are referenced.
- Clarify that all steps can be performed on Linux/macOS, and highlight any OS-specific differences.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for Azure portal, Azure CLI, ARM templates, and programming languages (.NET, JavaScript, Python, Java), but PowerShell examples are prominent and often shown alongside or before CLI examples. PowerShell is a Windows-centric tool, and its heavy inclusion may create friction for Linux/macOS users. Additionally, PowerShell is referenced in some CLI tabs (e.g., az identity create) with 'azurepowershell-interactive' code blocks, which could confuse non-Windows users. However, Azure CLI and ARM template instructions are present throughout, and most critical tasks can be completed cross-platform.
Recommendations
- Ensure all CLI code blocks use the correct 'azurecli-interactive' language tag, not 'azurepowershell-interactive', to avoid confusion.
- Where PowerShell is used, clarify its cross-platform availability (PowerShell Core) or recommend Azure CLI as the primary cross-platform tool.
- Consider showing Azure CLI examples before PowerShell, or explicitly note that PowerShell is optional and CLI is preferred for Linux/macOS.
- Add explicit notes or links for Linux/macOS users if any step is Windows-specific.
- Review and update any PowerShell-heavy sections to ensure CLI parity and clarity.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation is for a feature (gateway-required virtual network integration) that is explicitly Windows-only, as stated in the content. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, and Linux equivalents are not provided. Windows tools and patterns are mentioned first and exclusively, which may create friction for Linux/macOS users who need to troubleshoot related networking issues in hybrid environments.
Recommendations
- Clarify early and prominently that gateway-required virtual network integration is Windows-only, which is already done, but also note that troubleshooting steps are Windows-centric.
- Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (e.g., nc, curl, netstat, ss) for users who may be working in mixed environments.
- Mention that Linux App Service users should use regional virtual network integration and link to relevant documentation.
- For tools like tcpping and nameresolver, specify if they are available on Linux/macOS or provide alternatives.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux instructions using zone pivots, but in several shared sections, Windows/PowerShell examples are often presented before Linux/Bash equivalents. PowerShell commands are consistently included alongside Bash, and some sections (like persistent storage and memory/CPU settings) show Windows details or terminology first. There is also a slight emphasis on Windows tools and patterns (e.g., references to C:\home, IIS, .NET Framework, and Kudu) before their Linux alternatives, even in general sections.
Recommendations
- Where possible, alternate the order of Bash and PowerShell examples so Linux users see their platform first in some sections.
- Ensure that Linux-specific terminology (e.g., /home instead of C:\home) is used in Linux sections and not mixed with Windows paths.
- In shared sections, clarify when a feature or instruction is Windows- or Linux-specific, and avoid defaulting to Windows-first explanations.
- Consider adding more Linux-specific troubleshooting and diagnostic examples, similar to the detailed Kudu/PowerShell instructions for Windows.
- Review for any lingering references to Windows tools (e.g., IIS, .NET Framework) in general sections and move them to Windows-only pivots.