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 1951-1975 of 2121 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Path Patterns
Summary
The documentation generally covers Azure App Service backup features in a cross-platform manner, with Azure portal and Azure CLI instructions that work for both Windows and Linux apps. However, there are subtle signs of Windows bias: Windows file paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are referenced before Linux equivalents, and the Kudu DebugConsole example uses Windows-style paths. The documentation mentions uploading files via FTP, which is a common Windows pattern, but does not reference SFTP or Linux-native tools. PowerShell is mentioned as an automation option, but not prioritized over CLI. Linux paths and behaviors are referenced, but often after Windows ones.
Recommendations
- When referencing file paths, always show both Windows and Linux equivalents (e.g., %HOME%/site/wwwroot and /home/site/wwwroot).
- In examples and instructions, alternate between Windows and Linux paths, or show both side-by-side.
- Mention SFTP and Linux-native file upload tools alongside FTP.
- In the 'Automate with scripts' section, clarify that both Azure CLI and PowerShell are cross-platform, and provide links to Bash shell samples if available.
- When discussing Kudu DebugConsole, note that it works for both Windows and Linux apps, and show Linux path examples.
- Ensure screenshots and examples are balanced between Windows and Linux environments.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service plans, explicitly supporting both Windows and Linux. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (such as PowerShell, RDP, IIS customization, and .NET Framework) are described first and in detail, while Linux is mentioned only as a limitation. The rest of the page does not show significant Windows bias, and examples/tools are generally OS-neutral.
Recommendations
- When describing Managed Instance, clarify that its Windows focus is intentional and provide a brief note about Linux alternatives or equivalent Linux hosting options in Azure App Service.
- Ensure that links and feature tables consistently mention Linux parity or limitations where relevant.
- Add references or links to Linux-specific documentation for App Service plans, especially for users seeking OS customization or advanced networking on Linux.
- If possible, provide examples or guidance for Linux App Service plan scenarios alongside Windows examples.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for Azure portal, Azure CLI, ARM templates, and language SDKs, but PowerShell examples are prominent and often shown alongside or before CLI equivalents. PowerShell is a Windows-centric tool, and its heavy inclusion (especially in identity assignment/removal and token retrieval) may create friction for Linux/macOS users. However, Azure CLI and ARM template instructions are present for all critical tasks, and language SDK examples are cross-platform.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell examples, as CLI is cross-platform.
- Clearly indicate that PowerShell instructions are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Where PowerShell is not supported (e.g., user-assigned identity for App Service), highlight CLI as the preferred method.
- Consider adding Bash shell script examples for token retrieval, especially in sections where only PowerShell is shown.
- Review the 'Connect to Azure services in app code' section to ensure parity in scripting examples (e.g., show Bash/cURL alongside PowerShell).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance via pivot sections, but 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 examples are included alongside Bash, but Linux-specific tools (e.g., SSH setup, Docker Compose) are sometimes less prominent or appear later. Some sections (like customizing container memory and compute cores) use Windows terminology and tools, and Windows-specific features (like IIS integration) are described in detail, while Linux equivalents are less emphasized.
Recommendations
- Ensure Linux examples and guidance are presented with equal prominence and detail as Windows, especially in shared sections.
- Where PowerShell commands are given, provide equivalent Bash or Linux shell commands first or side-by-side.
- Expand Linux-specific guidance (e.g., parent images, troubleshooting, persistent storage) to match Windows detail.
- Clarify when features or instructions are Windows-only, and provide Linux alternatives or explicit notes when not applicable.
- Review the order of examples and tools to avoid Windows-first bias; alternate or parallelize Windows and Linux instructions.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for managing identities. However, PowerShell examples are prominent and often provided, which can be associated with Windows environments. In some sections, PowerShell is listed before CLI, and PowerShell-specific notes are included. There is no explicit mention of Linux/macOS-specific instructions or shell examples (e.g., Bash), but Azure CLI commands are cross-platform. The documentation does not use Windows-only tools or patterns, and the Azure CLI is included throughout, ensuring Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add Bash shell examples for token retrieval (e.g., using curl) alongside PowerShell examples.
- Where PowerShell is used, note its availability on Linux/macOS (via PowerShell Core), or provide equivalent Bash/Unix shell instructions.
- Consider listing Azure CLI examples before PowerShell to emphasize cross-platform support.
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. Azure PowerShell examples are consistently included and shown alongside Azure CLI, but there is no evidence of Windows-only tools or patterns being prioritized. However, PowerShell is a Windows-centric tool (though available cross-platform), and its inclusion may be seen as a mild Windows bias. The CLI examples are platform-neutral and always present. The order of examples (portal, CLI, PowerShell) puts Windows tools last, not first, so the bias is minimal. No critical steps are Windows-only, and Linux/macOS users can complete all tasks using the Azure portal or CLI.
Recommendations
- Explicitly note that Azure PowerShell is available cross-platform to reduce perceived Windows bias.
- Consider adding Bash shell scripting examples for Azure CLI usage to further emphasize Linux parity.
- Clarify that all CLI examples work on Linux/macOS and Windows equally.
- If possible, link to documentation about installing Azure CLI and Azure PowerShell on Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation for Azure App Service Plans is generally neutral, describing both Windows and Linux support. However, the 'Managed Instance on Azure App Service' section is Windows-only and is presented prominently, with Windows-specific features (PowerShell, RDP, IIS, .NET Framework) listed before any mention of Linux limitations. The main content does not provide platform-specific examples or tools, but the Windows-only Managed Instance section is not clearly separated as a Windows-specific feature, which could cause confusion.
Recommendations
- Clearly label the 'Managed Instance on Azure App Service' section as Windows-only at the start of the section.
- Add a brief note or comparison for Linux users, explaining the equivalent options or limitations for Linux App Service plans.
- Ensure links and feature tables consistently indicate OS support (Windows/Linux) where relevant.
- Consider adding Linux-specific examples or clarifications in sections that discuss features available on both platforms.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance via pivot sections, but in several areas, Windows-specific examples, tools, and terminology are presented first or more prominently. PowerShell commands are frequently included alongside Bash/Azure CLI, and Windows tools (like Kudu, IIS, .NET Framework, and Windows directory paths) are referenced in detail. Linux equivalents are present but sometimes less detailed or appear after Windows content.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with clear pivots.
- Where PowerShell commands are shown, always provide Bash/Azure CLI equivalents and clarify OS applicability.
- Expand Linux-specific guidance to match the depth of Windows sections (e.g., troubleshooting, diagnostic logs, persistent storage details).
- Avoid referencing Windows tools or patterns (like Kudu, C:\home, IIS) in Linux pivots unless Linux equivalents are also provided.
- Review ordering of sections/examples to avoid consistently presenting Windows content first.
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 (Python, Java, JavaScript, .NET), but PowerShell examples are prominent and often shown alongside or before CLI equivalents. PowerShell is a Windows-centric tool, and its heavy inclusion (especially with detailed scripts) may create friction for Linux/macOS users. However, Azure CLI and ARM template instructions are present throughout, and most critical tasks can be completed on Linux/macOS. Some sections (e.g., assigning user-assigned identities for App Service) note PowerShell limitations, but do not provide Linux-specific workarounds or alternatives.
Recommendations
- Ensure Azure CLI examples are always present and shown before PowerShell examples, as CLI is cross-platform.
- Where PowerShell is used, clarify its OS requirements and provide equivalent Bash or shell script examples for Linux/macOS users.
- Highlight that Azure CLI and ARM templates are fully supported on Linux/macOS, and recommend them as the primary automation tools.
- Add explicit notes or links for Linux/macOS users when PowerShell functionality is limited or unavailable.
- Consider including Bash shell script examples for token retrieval, especially in sections where only PowerShell is shown.
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 primarily Windows-centric and is presented alongside CLI in all code tabs. The PowerShell examples are not strictly necessary for Linux/macOS users, and their inclusion may suggest a Windows-first mindset. However, the CLI examples are always present and appear before PowerShell, ensuring Linux parity. No Windows-only tools or patterns are mentioned, and Linux-specific guidance is not missing.
Recommendations
- Consider clarifying that Azure PowerShell is available cross-platform, but Azure CLI is generally preferred for Linux/macOS users.
- Optionally, reorder code tabs to show Azure CLI before Azure PowerShell, emphasizing CLI as the default for non-Windows environments.
- Add a brief note in the prerequisites or migration steps indicating that all operations can be performed from Linux/macOS using Azure CLI.
- If possible, provide explicit guidance for Linux/macOS users in troubleshooting or post-migration sections (e.g., how to verify connectivity using Linux tools).
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux instructions using pivot sections, but in shared/general sections, Windows/PowerShell examples are often shown before Linux/Bash equivalents. PowerShell commands are frequently included alongside Bash, and some sections (like persistent storage and environment variables) mention Windows-specific tools and paths first. However, Linux parity is generally maintained, and Linux-specific instructions are present where needed.
Recommendations
- In shared sections, alternate the order of Bash and PowerShell examples, or present Bash (Linux/macOS) first to avoid implicit Windows prioritization.
- Where possible, clarify when a command or tool is cross-platform, and avoid defaulting to Windows terminology or paths in general guidance.
- Ensure that all features and examples have clear Linux/macOS equivalents, and that Linux-specific nuances are equally detailed.
- Review for subtle language that assumes Windows-first workflows (e.g., mentioning C:\home before /home in shared sections).
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for managing identities. However, PowerShell examples are prominent and often shown alongside or before CLI examples, and PowerShell is referenced in some CLI tabs (e.g., az identity create). There is a mild 'windows_first' bias in some sections, as PowerShell is presented as a primary scripting option, even though Azure CLI is cross-platform. No critical tasks are Windows-only, and Linux/macOS users can complete all steps using Azure CLI or ARM templates.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell examples, especially in tabbed sections.
- Clarify that Azure PowerShell is cross-platform, but highlight Azure CLI as the preferred option for Linux/macOS users.
- Remove PowerShell references from CLI tab examples (e.g., az identity create is shown as azurepowershell-interactive).
- Add explicit notes or guidance for Linux/macOS users where PowerShell is not supported or less common.
- Consider adding Bash script examples for common tasks, especially in sections where PowerShell is heavily used.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Minor Content Duplication
Summary
The documentation provides both Windows and Linux instructions using zone pivots, but there is a tendency to present Windows-specific details and PowerShell examples before or alongside Linux/Bash equivalents. Some sections, such as persistent storage and environment variables, repeat similar instructions for both platforms but often list Windows (and PowerShell) first. There are also Windows-specific tools and patterns (e.g., references to C:\home, IIS, .NET Framework, and PowerShell) that are more prominently described, while Linux equivalents are sometimes less detailed or appear after the Windows sections.
Recommendations
- Ensure Linux and Windows instructions/examples are presented with equal prominence, alternating which comes first or grouping by platform.
- Where both Bash and PowerShell commands are provided, consider listing Bash (Linux/macOS) first, or clearly labeling both as equally supported.
- Expand Linux-specific details where Windows-specific features (like IIS or .NET Framework) are described, or provide clear notes when a feature is Windows-only.
- Review for minor content duplication (e.g., persistent storage sections) and clarify differences between platforms to avoid confusion.
- In general sections (not under explicit platform pivots), avoid defaulting to Windows terminology (e.g., C:\home) without immediately providing the Linux equivalent (/home).
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 primarily used on Windows and is listed alongside CLI in every example. The PowerShell examples are not strictly Windows-only, but the documentation consistently presents PowerShell examples, which may create a perception of Windows bias. However, Linux/macOS users can fully complete all tasks using Azure CLI or portal, and no critical steps are Windows-only.
Recommendations
- Consider listing Azure CLI examples before Azure PowerShell to emphasize cross-platform parity.
- Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
- If possible, provide Bash shell script examples for common migration tasks to further support Linux users.
- Clarify that all steps can be completed on any OS using Azure CLI or portal.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux instructions using Azure CLI and PowerShell, and uses pivot sections to separate Windows and Linux-specific guidance. However, in several cross-platform sections, Windows/PowerShell examples are consistently presented before Linux/Bash equivalents. Some sections (e.g., persistent storage, environment variables, port configuration) show PowerShell commands immediately after Bash, and the Windows path (C:\home) is sometimes mentioned before the Linux path (/home). There are also several references to Windows-specific tools and patterns (e.g., IIS, .NET Framework, System.ConfigurationManager) in the main flow, with Linux equivalents only in pivoted sections or as afterthoughts.
Recommendations
- Alternate the order of Bash and PowerShell examples, or group them under clear OS-specific headings to avoid implicit prioritization.
- When referencing file paths, mention Linux and Windows equivalents together, or clarify which applies to which OS.
- Ensure that Linux-specific tools and patterns (e.g., OpenSSH, Linux environment variable conventions) are given equal prominence and not relegated to notes or after Windows sections.
- Where possible, provide Linux examples first in sections that are not inherently Windows-centric.
- Review pivoted content to ensure parity in depth and clarity between Windows and Linux sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
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 paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are used as primary examples, and references to Kudu DebugConsole and FTP upload methods are described using Windows-style paths. PowerShell is mentioned as an automation option alongside Azure CLI, but no Bash or Linux shell scripting examples are provided. The documentation does mention Linux app backup locations, but Windows patterns are presented first and more frequently.
Recommendations
- Provide Linux/macOS path examples (e.g., /home/site/wwwroot) alongside Windows paths in all relevant sections.
- Clarify that Kudu DebugConsole and FTP methods work for both Windows and Linux apps, and show Linux directory structures where appropriate.
- Add Bash or Linux shell scripting samples for automation, not just Azure CLI and PowerShell.
- When referencing environment variables, include both Windows (%HOME%) and Linux ($HOME) formats.
- Ensure that instructions for uploading files (e.g., _backup.filter) are clear for Linux users, including directory paths and tools.
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 relevant sections. However, PowerShell examples are consistently included alongside CLI, and the PowerShell examples are presented immediately after the CLI examples, which may subtly prioritize Windows tooling. There is no evidence of missing Linux examples, as Azure CLI is fully cross-platform and all CLI commands are present. No Windows-only tools or patterns are mentioned, and the content is not Windows-specific. However, the use of PowerShell as a primary scripting example may create minor friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Consider explicitly noting that Azure CLI is cross-platform and preferred for Linux/macOS users.
- If possible, provide Bash shell script examples for common migration steps, especially for tasks that may require scripting beyond Azure CLI.
- Clarify that PowerShell examples are optional and primarily for Windows users.
- Ensure that CLI examples are always shown before PowerShell, or provide a clear tabbed interface so users can easily select their preferred environment.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for configuring managed identities. However, PowerShell examples are prominent and often shown alongside or before CLI examples. In several sections, PowerShell is presented as a primary scripting option, which is most commonly used on Windows. Additionally, PowerShell is referenced for tasks where Azure CLI (cross-platform) is also available, but PowerShell is sometimes given more detailed coverage (e.g., for Functions). There is no explicit mention of Linux/macOS-specific tools or shell patterns, and the CLI examples do not reference Bash or other Linux shells. However, Azure CLI is included throughout, mitigating most friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell examples, especially for cross-platform tasks.
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and consider adding Bash shell context or notes for Linux/macOS users.
- Where PowerShell is used for scripting, add equivalent Bash or shell script examples for token retrieval and automation.
- Explicitly mention that Azure CLI and ARM templates are fully cross-platform.
- Review PowerShell-heavy sections for opportunities to add or prioritize CLI or Bash alternatives.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers Azure App Service plans for both Windows and Linux, with most sections being OS-neutral. However, the 'Managed Instance on Azure App Service (preview)' section is Windows-only and is described before any Linux-specific equivalents (if any exist), and Windows-specific features (like PowerShell scripts, RDP, IIS customization) are mentioned without Linux alternatives. The rest of the page is balanced, but Windows features are highlighted first in the Managed Instance section.
Recommendations
- Clearly label Windows-only sections (such as Managed Instance) to avoid confusion.
- If Linux equivalents exist (e.g., for OS customization, networking, or storage), mention them or link to relevant documentation.
- Add a brief note in the Managed Instance section clarifying that Linux users should refer to other hosting options.
- Ensure that links to pricing and feature tables include both Windows and Linux details.
- Consider adding a summary table comparing Windows and Linux plan features/capabilities.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance, but Windows-specific information and examples are often presented first, and PowerShell commands are frequently included alongside Bash/Azure CLI. Windows tools and concepts (such as IIS, .NET Framework, and Windows directory paths) are referenced more prominently and in greater detail. Linux parity is generally maintained, but Windows bias is evident in ordering and depth.
Recommendations
- Ensure Linux and Windows sections are equally detailed, especially regarding persistent storage, environment variables, and diagnostic logging.
- Present Linux and Windows examples side-by-side or alternate which comes first to avoid 'windows_first' bias.
- Expand Linux-specific troubleshooting and advanced configuration guidance to match Windows depth.
- Where possible, provide Linux-native command-line examples (e.g., Bash, Docker) before PowerShell, or at least equally.
- Clarify when features or settings differ between Windows and Linux, and link to Linux-specific resources where available.
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 code examples for Azure CLI, Azure PowerShell, and the Azure portal. While both CLI and PowerShell are supported, PowerShell examples are included throughout, and in some sections, PowerShell is listed after CLI but before or alongside portal instructions. The presence of PowerShell examples and the 'devx-track-azurepowershell' metadata may indicate a slight Windows bias, as PowerShell is more commonly used on Windows (though it is cross-platform). However, all critical steps are covered with Azure CLI and portal instructions, ensuring Linux/macOS users can complete the migration without issue.
Recommendations
- Continue to ensure all examples are provided for both Azure CLI and PowerShell, with clear indication that PowerShell Core is cross-platform.
- Consider explicitly stating that Azure PowerShell examples work on PowerShell Core (available on Linux/macOS) to reduce perceived Windows bias.
- Where possible, list Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- If any step is only possible via PowerShell, provide alternative guidance or clarify platform requirements.
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 for managing TLS/SSL certificates in Azure App Service, with most steps performed in the Azure Portal or using platform-agnostic tools (Azure CLI, OpenSSL). However, there are some signs of Windows bias: PowerShell examples are given alongside Azure CLI, and Windows tools (IIS, Certreq.exe) are mentioned for certificate export, with Linux equivalents not explicitly described. In some automation and export scenarios, Windows tools are referenced first or exclusively.
Recommendations
- When mentioning certificate export using IIS or Certreq.exe, also provide explicit Linux/macOS alternatives (e.g., OpenSSL commands for exporting PFX from PEM/CRT and key files).
- In automation sections, ensure that Azure CLI examples are shown before PowerShell, or clarify that both are equally supported.
- Where screenshots or UI steps are shown, clarify that the process is the same across platforms, or note any OS-specific differences.
- Add links or notes for Linux/macOS users on how to generate and manage certificates using OpenSSL or other common tools.
- In the FAQ and automation sections, ensure parity by providing Bash/CLI scripts where PowerShell is shown.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Path Patterns
Summary
The documentation provides both Windows and Linux guidance for Azure App Service backups, but there are several subtle Windows biases. Windows paths and environment variables (e.g., %HOME%, D:\home\site\wwwroot) are referenced first or exclusively in some sections. Kudu DebugConsole and FTP instructions use Windows-style paths. PowerShell is mentioned alongside Azure CLI, but Linux shell scripting is not. The documentation does mention Linux apps and containers, but Windows examples and terminology are often presented first or more prominently.
Recommendations
- Where file paths are referenced (e.g., %HOME%, D:\home\site\wwwroot), add Linux equivalents (/home/site/wwwroot) and clarify for cross-platform users.
- When describing access via Kudu DebugConsole or FTP, provide Linux path syntax and note differences for Linux-hosted apps.
- In the 'Automate with scripts' section, add Bash/shell scripting examples or clarify that Azure CLI works equally well on Linux/macOS.
- Review screenshots and instructions to ensure they are not Windows-centric, or add Linux-specific visuals where appropriate.
- Where environment variables are referenced, explain both Windows (%HOME%) and Linux ($HOME) conventions.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity across Azure Portal, Azure CLI, Azure PowerShell, and ARM template methods for managing identities. However, PowerShell examples are prominent and often provided, which may imply a Windows bias. In some sections, PowerShell is listed before other options, and PowerShell-specific notes are included. The CLI examples are cross-platform, but PowerShell is not available on all Linux/macOS systems by default. The documentation does not exclusively use Windows tools, but PowerShell is emphasized more than necessary for a cross-platform audience.
Recommendations
- Ensure Azure CLI examples are always listed before PowerShell, as CLI is cross-platform.
- Clarify that PowerShell examples are optional and provide guidance for Linux/macOS users on installing PowerShell if needed.
- Where possible, provide Bash shell examples for Linux/macOS users, especially for token retrieval and scripting.
- Add explicit notes about cross-platform compatibility for each tool, highlighting CLI and ARM templates as platform-neutral.
- Review and balance the order and prominence of PowerShell and CLI examples to avoid implying Windows is preferred.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally presents Azure App Service Plans in a cross-platform manner, mentioning both Windows and Linux support. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (e.g., PowerShell, RDP, .NET Framework) are described first and in detail, with Linux explicitly noted as unsupported only at the end. The main documentation otherwise avoids Windows bias.
Recommendations
- In the 'Managed Instance' section, clarify at the beginning that this is a Windows-only feature to avoid confusion for Linux users.
- Where possible, provide parity or alternative guidance for Linux users, or explicitly state when a feature is not available for Linux.
- Ensure that links to plan details and pricing clearly distinguish between Windows and Linux options.
- Consider adding a short comparison table or callout summarizing which features are Windows-only versus cross-platform.