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 1976-2000 of 2121 flagged pages
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for Azure CLI, PowerShell, ARM templates, and portal usage. However, PowerShell examples are prominent and often shown alongside or before CLI examples. The PowerShell section is detailed, and some tasks (e.g., assigning user-assigned identity for App Service) are noted as not supported in PowerShell, but alternatives are given. There is a slight bias in favor of PowerShell, which is more commonly used on Windows, and PowerShell is listed as a separate tab for token retrieval, even though the CLI and HTTP methods are cross-platform. The ordering of examples sometimes puts PowerShell before CLI, and PowerShell is referenced in code blocks for Azure CLI (likely a documentation error). However, Linux/macOS users can complete all tasks using Azure CLI, ARM templates, or HTTP requests.
Recommendations
- Ensure Azure CLI examples are always present and shown before or alongside PowerShell examples, as CLI is cross-platform.
- Correct any code block labeling errors (e.g., Azure CLI sections labeled as 'azurepowershell-interactive').
- Explicitly mention that Azure CLI works on Linux/macOS and is recommended for cross-platform scenarios.
- Add brief notes to PowerShell sections indicating that PowerShell Core is available for Linux/macOS, or link to CLI alternatives.
- Review the ordering of tabs to avoid implicit prioritization of Windows tools.
Create Pull Request
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 (PowerShell), and terminology are often presented first or in greater detail. PowerShell commands are given alongside Bash/Azure CLI, but Windows-centric concepts (like IIS, .NET Framework, C:\home, Windows Server images) are described in depth, sometimes before Linux equivalents. Some sections (e.g., parent images, persistent storage) focus heavily on Windows before Linux, and troubleshooting/logging references Windows paths and tools. Linux parity is generally good, but Windows bias is evident in ordering and example prominence.
Recommendations
- Ensure Linux examples and terminology are presented with equal prominence and detail as Windows sections.
- Where possible, alternate the order of Windows and Linux pivots or provide a neutral introduction before splitting into OS-specific guidance.
- Expand Linux-specific troubleshooting, logging, and persistent storage details to match Windows depth.
- Avoid referencing Windows tools (e.g., PowerShell, IIS) in general sections unless a Linux equivalent is also provided.
- Review section ordering to avoid Windows-first bias, especially in shared guidance (e.g., parent images, environment variables, persistent storage).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is structured to support both Windows and Linux containers via pivot sections, but there are several signs of Windows bias. Windows-specific information and examples (such as PowerShell commands, Windows parent images, IIS/.NET Framework details, and Windows directory paths) are often presented first or in greater detail. PowerShell commands are given alongside Bash/Azure CLI, but sometimes Windows-specific tools and patterns (like Kudu, C:\home, and Windows memory/core settings) are emphasized. Linux equivalents are present but sometimes less detailed or appear after Windows content.
Recommendations
- Ensure Linux and Windows examples are equally detailed and presented in parallel, not always Windows-first.
- Where PowerShell commands are given, provide equivalent Bash or Linux shell commands with equal prominence.
- Expand Linux-specific guidance (e.g., persistent storage, diagnostic logs, SSH setup) to match the depth of Windows sections.
- Review pivoted content for parity: ensure Linux pivots are as comprehensive as Windows pivots.
- Where possible, mention Linux tools and patterns before or alongside Windows ones, especially in general sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Path Patterns
Summary
The documentation provides both Azure portal and Azure CLI instructions, which are cross-platform. However, there are several subtle signs of Windows bias: Windows file paths and environment variables (e.g., `%HOME%`, `D:\home\site\wwwroot\`), references to Kudu DebugConsole (which is more familiar to Windows users), and FTP upload instructions using Windows-style paths. Linux paths and equivalents are mentioned but generally after Windows examples. The documentation does not provide explicit Linux/macOS-specific instructions or examples for file operations, and Windows path conventions are used throughout.
Recommendations
- Add Linux/macOS path examples alongside Windows paths (e.g., `/home/site/wwwroot/` instead of only `D:\home\site\wwwroot\`).
- Clarify that `%HOME%` is equivalent to `/home` for Linux App Service apps.
- Provide explicit instructions for uploading files using Linux/macOS tools (e.g., SCP, SFTP, or Azure CLI) in addition to FTP.
- Mention that Kudu DebugConsole is available for both Windows and Linux App Service apps, and provide Linux-specific navigation tips if applicable.
- Where file paths are referenced, show both Windows and Linux formats in tables or code blocks.
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 Azure CLI, PowerShell, and portal instructions for all major steps. While both CLI (cross-platform) and PowerShell (Windows-centric) examples are present, PowerShell examples are always shown after CLI, and there are no steps or examples that are Windows-only. However, the presence of PowerShell examples throughout, and the explicit mention of Azure PowerShell in the metadata, may create a slight perception of Windows bias, especially since PowerShell is more commonly used on Windows. All features and instructions are available to Linux/macOS users via the Azure CLI and portal.
Recommendations
- Continue to provide Azure CLI and portal instructions for all steps, as these are cross-platform.
- Consider clarifying that Azure PowerShell is available cross-platform (Windows, macOS, Linux) to reduce perception of Windows bias.
- If possible, mention that all migration steps can be performed from Linux/macOS using the Azure CLI or portal.
- Ensure that any future advanced troubleshooting or scripting examples also include Bash/CLI equivalents if PowerShell is used.
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
Powershell Heavy
Windows First
Summary
The documentation provides example commands for Azure CLI and Azure PowerShell in parallel, but PowerShell examples are always present and often shown after CLI, which can be interpreted as a slight Windows-first bias. There is no explicit Linux/macOS example section, and PowerShell is a Windows-native tool (though available cross-platform). However, all critical steps are covered with Azure CLI, which is fully supported on Linux/macOS, and there are no tasks that require Windows-only tools.
Recommendations
- Clarify in the introduction or relevant sections that Azure CLI commands are fully supported on Linux and macOS.
- Consider adding a short note that PowerShell Core is available cross-platform, or clarify that the PowerShell examples work on all supported platforms.
- If possible, add explicit bash/shell script examples for common Linux/macOS workflows, or at least mention that Azure CLI is the recommended tool for Linux/macOS users.
- Ensure that the order of examples does not consistently favor Windows tools (e.g., sometimes show CLI before PowerShell, or group them as 'cross-platform').
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
Powershell Heavy
Windows First
Summary
The documentation provides example commands for Azure CLI, Azure PowerShell, and the Azure portal in parallel. However, PowerShell examples are always present and shown alongside CLI, which may be perceived as Windows-centric. The PowerShell examples are not explicitly marked as Windows-only, and their presence may suggest a slight Windows-first bias. However, Azure CLI is fully cross-platform and is given equal prominence. No critical steps are Windows-only, and Linux users can complete all tasks using the CLI or portal.
Recommendations
- Clearly indicate that Azure PowerShell is available cross-platform (Windows, macOS, Linux) to reduce perceived Windows bias.
- Consider listing Azure CLI examples before PowerShell examples, as CLI is the default for many Linux/macOS users.
- Explicitly state that all operations can be performed from any OS using Azure CLI or the portal.
- If possible, add a short note explaining the equivalence of CLI and PowerShell for all supported platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers Azure App Service plans for both Windows and Linux, with most content being OS-neutral. However, the 'Managed Instance on Azure App Service (preview)' section is Windows-only and is presented before any Linux-specific features or parity notes. The main links and examples reference Windows pricing and features first, but do not exclude Linux users from completing the tasks described.
Recommendations
- Add explicit Linux parity notes or links where relevant, especially in sections discussing features or pricing tiers.
- Ensure that examples and feature lists mention Linux support and limitations alongside Windows, rather than after or not at all.
- Provide links to Linux-specific documentation or guidance where Managed Instance or other Windows-only features are discussed.
- Clarify in the Managed Instance section that this feature is Windows-only and direct Linux users to alternative options.
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 command-line examples for Azure CLI and Azure PowerShell in all relevant sections. Azure PowerShell examples are consistently included and shown after Azure CLI, but there is no explicit Linux/macOS bias or omission. However, PowerShell is a Windows-centric tool (despite cross-platform support), and its inclusion may suggest a Windows-first mindset. The documentation does not reference Windows-specific tools or patterns, nor does it omit Linux/macOS equivalents. Azure CLI is cross-platform and is always presented first, minimizing friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, not just on Windows.
- Consider adding Bash shell script examples (where relevant) to further support Linux/macOS users.
- Explicitly mention that all Azure CLI commands are fully supported on Linux and macOS.
- If possible, provide links to installation guides for Azure CLI and Azure PowerShell on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service plans, explicitly mentioning both Windows and Linux options. However, the 'Managed Instance on Azure App Service' section is Windows-only and is presented before any Linux-specific features or equivalents, which could create a perception of Windows-first bias. No PowerShell-heavy examples, Windows tools, or missing Linux examples are found elsewhere in the document.
Recommendations
- Clearly label Windows-only preview features (such as Managed Instance) as such, and consider placing them in a dedicated section or appendix to avoid confusion.
- Add a brief statement clarifying Linux parity and limitations, especially for preview features.
- If Linux-specific advanced hosting options exist or are planned, mention them for parity.
- Ensure links to plan details and pricing cover both Windows and Linux options equally.
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 generally provides cross-platform guidance, especially for certificate creation and management, with clear OpenSSL (Linux/macOS) and Azure CLI examples. However, there are several instances where Windows tools (IIS, Certreq.exe, PowerShell) are mentioned as primary or alternative methods, sometimes before Linux equivalents. In automation and permission assignment sections, both Azure CLI and PowerShell are shown, but PowerShell is given a dedicated section. The export instructions for certificates reference IIS and Certreq.exe for Windows users, while OpenSSL is used for Linux/macOS. The FAQ and automation sections also provide both Azure CLI and PowerShell links, but PowerShell is sometimes listed first.
Recommendations
- Ensure that Linux/macOS tools (like OpenSSL) are always mentioned alongside Windows tools (IIS, Certreq.exe) and not as an afterthought.
- When listing automation or scripting options, alternate the order between Azure CLI and PowerShell, or group them together as 'cross-platform options' rather than defaulting to PowerShell/Windows-first.
- Where possible, provide explicit Linux/macOS GUI or workflow equivalents if Windows GUI tools (like IIS) are referenced.
- Clarify in each section that both Windows and Linux/macOS users are supported, and highlight any OS-specific limitations up front.
- If a Windows tool is referenced (e.g., IIS, Certreq.exe), provide a direct Linux/macOS alternative in the same context, not just as a secondary note.
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 Azure CLI, Azure PowerShell, and Azure Portal instructions for all migration steps. While both CLI and PowerShell are covered, PowerShell examples are consistently present and shown after CLI, and the documentation metadata includes 'devx-track-azurepowershell', suggesting a slight preference for PowerShell. However, Azure CLI examples are present and fully functional for Linux/macOS users, and no steps are Windows-only. The ordering of examples (CLI before PowerShell) is appropriate, but the inclusion of PowerShell in every example may indicate a minor Windows bias.
Recommendations
- Ensure Azure CLI examples are always present and complete (which is currently the case).
- Consider explicitly stating that Azure CLI is cross-platform and preferred for Linux/macOS users.
- If possible, add Bash or shell script snippets for common tasks to further improve Linux parity.
- Clarify in introductory sections that all steps can be completed on Linux/macOS using Azure CLI.
- Review metadata and tags to ensure CLI parity is emphasized alongside PowerShell.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation for Azure App Service Plans is generally cross-platform, referencing both Windows and Linux as supported operating systems. However, there is a minor bias in the 'Managed Instance on Azure App Service (preview)' section, which is Windows-only and described before clarifying its exclusivity. The rest of the document does not show significant bias; examples and features are presented in a platform-neutral manner, and there are no PowerShell-heavy or Windows-tools-centric instructions.
Recommendations
- Explicitly clarify Windows-only features (such as Managed Instance) at the start of relevant sections to avoid confusion for Linux users.
- Where platform-specific features are discussed, provide clear cross-references or alternatives for Linux users, or state that no equivalent exists.
- Ensure that links to pricing and feature tables include both Windows and Linux tabs or sections, if available.
- Continue to present platform options (Windows, Linux) together when listing capabilities or configuration steps.
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 Azure CLI, Azure PowerShell, and Azure Portal instructions for all major steps. However, PowerShell examples are always present and shown after CLI, and the documentation does not explicitly mention Linux/macOS environments or provide shell-specific guidance for those platforms. The use of PowerShell as a primary scripting example may create friction for Linux/macOS users, though Azure CLI is cross-platform and included throughout. There are no Windows-only tools or patterns, and Linux support is explicitly referenced in feature tables.
Recommendations
- Add explicit notes that Azure CLI commands work on Linux/macOS and Windows, and clarify that PowerShell examples are for Windows and PowerShell Core users.
- Consider including Bash or shell script examples for common Linux/macOS workflows, or clarify that Azure CLI is the recommended approach for cross-platform automation.
- Reorder examples to show Azure CLI first, as it is cross-platform, and clarify the intended audience for PowerShell examples.
- Add a brief section or note for Linux/macOS users confirming that all migration steps can be performed using Azure CLI on their platforms.
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 Windows and Linux-friendly instructions for most certificate management tasks, but there is a mild bias toward Windows. Windows tools (IIS, Certreq.exe) are mentioned before Linux alternatives, and PowerShell examples are given alongside Azure CLI, but not Bash or Linux-native commands for Azure resource management. Export instructions for certificates reference Windows tools first, with OpenSSL (Linux/macOS) covered second. No critical steps are Windows-only, but Windows patterns are presented before Linux equivalents.
Recommendations
- Present Linux/OpenSSL instructions before or alongside Windows/IIS/Certreq.exe steps for certificate export.
- Include Bash/Azure CLI examples for resource management tasks (e.g., role assignment, certificate binding) before or alongside PowerShell.
- Explicitly mention that all steps can be performed on Linux/macOS where applicable.
- Add links to Linux/macOS certificate management documentation where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally presents Azure App Service plans in a cross-platform manner, mentioning both Windows and Linux as supported operating systems. However, the 'Managed Instance on Azure App Service' section is Windows-only and features Windows-specific tooling (PowerShell, RDP, IIS, registry, MSI installers) without Linux equivalents or parity notes. While this is clearly marked as a Windows-only preview feature, the documentation could better clarify Linux limitations and alternatives for similar scenarios. Additionally, some links (such as pricing details) default to Windows tabs, and there are no explicit Linux-focused examples or guidance for scaling, cost, or feature parity.
Recommendations
- Explicitly clarify in the 'Managed Instance' section that Linux users should use other hosting options, and link to Linux/container alternatives.
- Where features or examples are Windows-only, add notes or links to equivalent Linux guidance (if available) or state that no equivalent exists.
- Ensure pricing and feature comparison links include Linux tabs or direct users to Linux-specific documentation.
- Add Linux-specific examples or callouts in general sections (e.g., scaling, cost, deployment slots) to demonstrate parity.
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 Azure CLI and PowerShell examples for all major steps, with PowerShell examples shown alongside CLI and portal instructions. While the page is not Windows-only, PowerShell is a Windows-centric tool (though available cross-platform), and its inclusion may suggest a slight Windows bias. However, Azure CLI examples are present and shown before PowerShell, and all instructions are applicable to both Linux and Windows users. No critical Linux examples are missing, and no Windows-only tools or patterns are mentioned.
Recommendations
- Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid the perception of Windows exclusivity.
- Consider including Bash script examples or explicit Linux/macOS command-line instructions where relevant, especially for common tasks.
- Add a note or section highlighting that all Azure CLI commands work natively on Linux/macOS, and PowerShell Core is supported on those platforms.
- Ensure parity in troubleshooting or advanced configuration examples, referencing Linux/macOS tools if applicable.
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 examples for Azure portal, Azure CLI, and Azure PowerShell for all major steps. However, PowerShell examples are always included and shown after CLI, and the CLI examples use Azure CLI (which is cross-platform), but there is a subtle bias in the ordering and inclusion: PowerShell is a Windows-centric tool, and its inclusion in every example may signal a slight Windows-first mindset. The documentation does not omit Linux/macOS-compatible instructions, as Azure CLI is fully supported on those platforms. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive.
Recommendations
- Consider clarifying that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid the impression that it is Windows-only.
- Explicitly mention that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
- If possible, alternate the order of CLI and PowerShell examples, or group them under 'cross-platform' and 'Windows PowerShell' headings.
- Add a brief note for Linux/macOS users confirming that all steps can be completed using Azure CLI.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally neutral regarding Windows and Linux, describing App Service plans and their features for both operating systems. However, there is some Windows bias in the 'Managed Instance on Azure App Service (preview)' section, which is Windows-only and highlights Windows-specific features and tools (e.g., PowerShell, RDP, IIS customization) without mentioning Linux equivalents or alternatives. Additionally, links such as 'App Service plan details' point to Windows pricing by default, and there are no Linux-specific examples or explicit parity notes for features that differ between OSes.
Recommendations
- Clearly indicate when features (such as Managed Instance) are Windows-only and provide links or notes about Linux alternatives or roadmap if available.
- Where possible, include Linux-specific examples, especially for configuration, scaling, and deployment scenarios.
- Ensure pricing and feature comparison tables reference both Windows and Linux plans, or clarify differences.
- Add parity notes for features that differ between Windows and Linux (e.g., supported runtimes, networking, scaling options).
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 First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides cross-platform guidance, but there are subtle biases. In automation examples, both Azure CLI and PowerShell are shown, but PowerShell is given its own dedicated section and is often listed second, which is a minor 'windows_first' bias. In the certificate export section, Windows tools (IIS, Certreq.exe) are mentioned for exporting certificates, but Linux/macOS equivalents are not explicitly referenced. There is a link to OpenSSL commands (cross-platform), but the Windows-specific tools are called out by name. The FAQ and automation sections also highlight PowerShell scripts alongside Azure CLI, but do not mention Bash or Linux-native scripting. Overall, Linux and macOS users can complete all tasks, but may need to infer or adapt some steps.
Recommendations
- When referencing certificate export tools, explicitly mention Linux/macOS equivalents (e.g., 'use OpenSSL on Linux/macOS, or IIS/Certreq.exe on Windows').
- In automation sections, provide Bash script examples or clarify that Azure CLI commands work on all platforms.
- When listing PowerShell, always pair with Azure CLI and clarify cross-platform compatibility.
- Consider adding a short section or callout for Linux/macOS users, especially for certificate preparation and export steps.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium v4 app creation, but lists PowerShell as a primary automation method alongside CLI. PowerShell is a Windows-centric tool, while CLI is cross-platform. The CLI examples are present and correct, but PowerShell is mentioned equally, which may imply parity or preference for Windows users. Additionally, in the 'Premium v4 availability' section, the Windows SKU CLI command is shown before the Linux SKU CLI command, indicating a slight 'windows_first' ordering bias.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows environments.
- Consider listing CLI examples before PowerShell examples to reinforce cross-platform parity.
- Explicitly state that all CLI commands work on Linux/macOS and Windows, and provide any Linux/macOS-specific notes if needed.
- Ensure that Linux-specific instructions (such as for custom containers) are as detailed as Windows instructions where relevant.
Low 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 PowerShell examples are consistently shown after CLI and are included in all relevant sections. There is a slight 'windows_first' bias in that PowerShell is always present, but Linux/macOS users are not left without guidance, as CLI and bash examples are provided. No critical tasks are Windows-only, and Linux parity is generally maintained.
Recommendations
- Consider explicitly noting that Azure CLI commands work cross-platform (Windows, Linux, macOS) to reassure non-Windows users.
- Where PowerShell examples are given, clarify that Azure CLI is the recommended cross-platform approach.
- Add a brief note or table summarizing which commands are platform-agnostic and which are Windows-specific.
- Ensure that bash/CLI examples are always shown first, or at least equally prominent, to avoid perception of Windows-first bias.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows a mild Windows bias: Windows SKU availability is listed before Linux, Azure PowerShell examples are provided alongside Azure CLI, and Windows terminology/tools (PowerShell, Windows SKUs) are referenced first or more prominently. However, Linux equivalents are present, and Azure CLI (cross-platform) is featured. No critical Linux omissions are found.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid Windows-first bias.
- Explicitly mention that Azure CLI works on Linux/macOS/Windows and is recommended for cross-platform automation.
- Provide bash shell script examples for Linux/macOS users, not just Azure CLI and PowerShell.
- Clarify when features or commands are OS-specific, and highlight Linux/macOS compatibility where relevant.
- Consider adding screenshots or instructions for Linux/macOS environments, not just portal UI (which is OS-neutral but often shown from Windows).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating App Service plan creation, but the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool. The ordering of examples is CLI first (cross-platform), then PowerShell (Windows). There are no Linux-specific shell examples (e.g., Bash), but CLI is cross-platform. The screenshots and portal instructions are platform-neutral. There is a slight bias in mentioning PowerShell as an automation option, which may imply Windows preference.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly mention that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
- Consider adding a Bash script example for Linux users, or note that Azure CLI commands can be used in Bash/zsh/fish shells.
- If mentioning PowerShell, add a note about its cross-platform availability to avoid implying it is Windows-only.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page displays a mild Windows bias: Windows instructions and tooling (Visual Studio, Kudu, PowerShell/CMD) are presented first or with more detail, while Linux equivalents (Oryx, Azure CLI, Cloud Shell) are present but sometimes less emphasized. Windows-specific tools and patterns are mentioned before Linux alternatives, and examples for Windows (such as using Kudu and PowerShell) appear before Linux instructions. However, Linux instructions are provided for all major tasks, and there are dedicated Linux sections.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and detail.
- Provide Linux examples and tools (such as Oryx, Azure CLI) before or alongside Windows tools, not after.
- Include explicit references to Linux-native development environments (e.g., VS Code, CLI workflows) where Visual Studio is mentioned.
- Expand Linux-specific troubleshooting and diagnostic guidance to match Windows coverage.
- Avoid assuming Visual Studio as the default tool; mention cross-platform alternatives.
- Where possible, unify instructions so that platform-specific pivots are not always Windows-first.