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 1926-1950 of 2121 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides a generally cross-platform overview of Azure App Service backup and restore, but exhibits mild Windows bias. Windows-specific paths (e.g., %HOME%, D:\home\site\wwwroot), references to Windows tools (Kudu DebugConsole, FTP), and Windows examples (e.g., MySQL in-app for Web Apps (Windows)) are presented before or more prominently than their Linux equivalents. PowerShell is mentioned alongside Azure CLI, but Linux-specific scripting or shell examples are absent. Linux paths and behaviors are referenced, but less frequently and often after Windows examples.
Recommendations
- Provide Linux/macOS-specific examples and paths (e.g., /home/site/wwwroot) alongside Windows paths.
- Clarify that tools like Kudu DebugConsole and FTP are available for both Windows and Linux App Service apps.
- Add Linux/macOS shell scripting examples where PowerShell is referenced.
- Ensure that Linux app backup/restore workflows are equally detailed and illustrated.
- Mention Linux-specific nuances (e.g., file permissions, case sensitivity) where relevant.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux-specific sections using pivot blocks, ensuring parity in most areas. However, in shared/general sections, Windows examples (e.g., PowerShell commands) are often presented before Linux/Bash equivalents. Some advanced configuration and diagnostic instructions (such as memory and CPU limits, and Kudu/PowerShell-based diagnostics) are more detailed for Windows containers. PowerShell commands are consistently shown alongside Bash, but Bash is not always shown first. There is a slight preference for Windows tools and patterns in the ordering and depth of examples.
Recommendations
- In shared/general sections, present Bash/Linux commands before or alongside PowerShell/Windows commands to avoid implicit prioritization.
- Ensure that advanced configuration and diagnostic instructions are equally detailed for both Linux and Windows containers, or clearly indicate platform limitations.
- Where possible, provide Linux-native troubleshooting and diagnostic tool instructions (e.g., using Linux shell commands in Kudu/SSH for Linux containers).
- Review the order of platform-specific sections to alternate or balance Windows and Linux coverage.
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. While both tools are cross-platform, PowerShell is historically associated with Windows and is listed after Azure CLI in each example. No Linux-specific tools or shell commands (such as Bash) are provided, but Azure CLI is available on Linux/macOS. The documentation does not show explicit Windows bias in content or features, but the inclusion of PowerShell examples may create a slight Windows-centric impression.
Recommendations
- Clarify that Azure CLI and PowerShell are both cross-platform and available on Linux/macOS.
- Consider adding Bash shell script examples for common tasks, or explicitly mention that Azure CLI commands can be run from Bash on Linux/macOS.
- If possible, provide brief notes about CLI usage on Linux/macOS (e.g., installation links, shell compatibility).
- Ensure parity in troubleshooting and post-migration steps for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity between Azure CLI and Azure PowerShell for most tasks, but PowerShell examples are given their own sections and are sometimes more detailed. In some cases, PowerShell is referenced before CLI, and there are explicit notes about PowerShell limitations. However, the CLI examples are present and usable on Linux/macOS, and ARM template instructions are platform-neutral. There are no Windows-only tools or patterns, and the documentation does not assume Windows as the default platform.
Recommendations
- Ensure Azure CLI examples are always presented before or alongside PowerShell examples, especially in sections where PowerShell is currently given prominence.
- Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Where PowerShell is used for scripting, consider providing Bash equivalents for token retrieval or other scripting tasks.
- Add explicit notes or links for Linux/macOS users if any step is platform-specific or if there are known limitations.
- Review the 'PowerShell' tab in the 'Connect to Azure services in app code' section and consider adding Bash/cURL examples for token retrieval.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers Azure App Service Plans for both Windows and Linux, but certain sections (such as Managed Instance) are Windows-only. However, the main content does not show significant Windows bias: it mentions both OS options, does not prioritize Windows tools or patterns, and does not provide Windows/PowerShell examples exclusively. The only minor bias is that Windows is listed first in the 'Operating system' bullet, and the Managed Instance section is Windows-only (which is appropriate, as noted).
Recommendations
- Where OS options are listed, alternate the order (e.g., 'Linux, Windows') or clarify parity where possible.
- If future examples or CLI instructions are added, ensure both Windows and Linux (Bash) examples are provided.
- Add links to Linux-specific App Service documentation or highlight feature parity between Windows and Linux plans.
- Clarify that Managed Instance is intentionally Windows-only and provide a pointer to Linux/container alternatives if available.
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service virtual network integration, with most concepts and instructions applicable to both Windows and Linux. However, in the 'Windows Containers specific limits' section, Windows container scenarios are described first and in detail, while Linux container limits are not discussed. Additionally, the troubleshooting section includes Azure CLI (bash) examples, which are cross-platform, and Linux continuous deployment is explicitly mentioned. Overall, the bias is minor and limited to Windows container details being presented first and more thoroughly.
Recommendations
- Add a comparable section detailing subnet/IP requirements and networking unit calculations for Linux containers, if applicable.
- Ensure parity in container-specific guidance by clarifying any Linux container limitations or requirements.
- Where Windows-specific limits are discussed, provide a clear statement if Linux containers do not have similar constraints, or link to Linux container documentation.
- Consider presenting container-specific limits in a way that makes clear which guidance applies to Windows, Linux, or both.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance using pivot sections, but in shared sections, Windows/PowerShell examples are often shown before Linux/Bash equivalents. There is a notable emphasis on PowerShell commands alongside Azure CLI, and some sections (e.g., persistent storage, environment variables, port configuration) consistently present Windows/PowerShell commands first. Additionally, Windows-specific tools and patterns (like references to C:\home, IIS, and .NET Framework) are described in detail, sometimes before or with more context than their Linux counterparts.
Recommendations
- In shared sections, alternate the order of Bash and PowerShell examples, or present Bash/Linux examples first to balance the experience.
- Where possible, group platform-specific instructions under clear subheadings or tabs, so users can easily find their relevant OS guidance.
- Ensure Linux-specific details (such as /home directory usage, Linux logging, and SSH setup) are as comprehensive and visible as Windows details.
- Reduce the prominence of PowerShell examples in general sections, or clearly mark them as optional/alternative to Bash/Azure CLI.
- Review for any subtle prioritization of Windows tools/patterns in introductory or summary paragraphs and ensure parity in Linux coverage.
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 portal, Azure CLI, and Azure PowerShell examples for all procedural steps. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows and is presented alongside CLI in all code sections. In several places, PowerShell examples are given equal prominence to CLI, which may subtly reinforce Windows-centric workflows. However, Linux/macOS users can fully complete all tasks using the Azure portal or CLI, and there are no Windows-only tools or patterns required.
Recommendations
- Consider listing Azure CLI examples before PowerShell in all code sections to reinforce CLI as the cross-platform default.
- Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional for those on Windows.
- If possible, clarify that all migration steps can be completed on any OS using Azure CLI or portal.
- Add a brief section or note about using Bash or other shells for scripting on Linux/macOS, if relevant.
App Service
Authentication and Authorization
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service authentication and authorization features for both Windows and Linux/container deployments. However, in the 'Feature architecture' section, the Windows (IIS module) implementation is described first, followed by the Linux/container implementation. There are no Windows-only examples, tools, or PowerShell-heavy instructions. All CLI examples use Azure CLI, which is cross-platform. No Linux/macOS equivalents are missing, and Linux/container scenarios are explicitly addressed.
Recommendations
- Consider describing the Linux/container architecture before or alongside the Windows architecture to avoid subtle ordering bias.
- Continue to ensure all CLI instructions use Azure CLI and avoid Windows-only tooling.
- Where relevant, provide explicit examples for Linux/container deployments, especially for configuration or troubleshooting steps.
- Maintain parity in troubleshooting/logging guidance for both Windows (IIS) and Linux/container environments.
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 sometimes shown before CLI, and PowerShell is referenced heavily for certain operations (e.g., assigning identities to Azure Functions). Azure CLI examples are present and generally cross-platform, but PowerShell is still emphasized, which may create friction for Linux/macOS users. No Windows-only tools or patterns are mentioned, and there are no missing Linux examples, but PowerShell's prominence and occasional first placement indicate a mild Windows bias.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell, as CLI is fully cross-platform.
- Clarify in sections where PowerShell is used that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Where PowerShell is not supported (e.g., assigning user-assigned identity in App Service), explicitly state alternatives for Linux/macOS users.
- Consider adding Bash shell scripting examples for common tasks, especially in sections where PowerShell scripts are provided.
- Review and balance the order of examples so that cross-platform tools (CLI, ARM templates) are not secondary to PowerShell.
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 platform. However, Windows-specific examples, tools, and explanations (such as PowerShell commands, Windows container base images, IIS/.NET Framework integration, and Windows directory paths) are often presented first or in greater detail. PowerShell commands are consistently provided alongside Bash/Azure CLI, but sometimes Windows-specific tooling (like System.ConfigurationManager, IIS, and Windows directory paths) is emphasized. Linux parity is generally good, but some Windows concepts are explained more thoroughly or appear before their Linux equivalents.
Recommendations
- Ensure Linux examples and explanations are as detailed as Windows ones, especially for persistent storage and environment variable injection.
- Where possible, present Linux and Windows examples side-by-side, rather than Windows first.
- Expand Linux-specific troubleshooting and advanced configuration sections to match Windows coverage (e.g., diagnostic logs, memory/cpu customization).
- Clarify differences in persistent storage paths and behaviors for Linux vs Windows, avoiding references to Windows paths in Linux sections.
- Add more Linux-specific examples for advanced scenarios (e.g., customizing container resources, health ping behavior, diagnostic log access).
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 PowerShell examples for assigning Key Vault permissions, but PowerShell is given equal prominence and is mentioned in headings and code tabs. There are also references to Windows-specific tools (IIS, Certreq.exe) for certificate export, and the PowerShell script is shown before any Linux-native scripting. However, the documentation does include OpenSSL-based instructions for certificate preparation, which is cross-platform and Linux-friendly. The FAQ and automation sections reference both Azure CLI and PowerShell, but the PowerShell example is called out explicitly in the FAQ link text.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
- Where Windows-specific tools (IIS, Certreq.exe) are mentioned, provide explicit Linux/macOS alternatives or clarify that OpenSSL is the recommended cross-platform approach.
- In automation/FAQ sections, reference Azure CLI as the primary example and PowerShell as an alternative for Windows users.
- Review all code tabs and ensure that Linux/macOS users are not required to use Windows tools at any step.
- Where possible, add bash scripting examples for common tasks (e.g., certificate binding) to further support Linux users.
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 appear before CLI examples, and PowerShell is referenced heavily, which may suggest a Windows-centric approach. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is still presented as a primary scripting option. There are no explicit Linux/macOS-only gaps, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but highlight Azure CLI as the default for scripting on Linux/macOS.
- Add explicit notes or links for Linux/macOS users where relevant, e.g., installation instructions for Azure CLI and PowerShell Core.
- Consider including Bash shell script examples for token retrieval, especially in the 'Connect to Azure services in app code' section.
- Review related tutorials and ensure they include non-Windows language examples (e.g., Python, Java, JavaScript) and CLI instructions.
App Service
Integrate your app with an Azure virtual network
...main/articles/app-service/overview-vnet-integration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure App Service virtual network integration. However, there is a section ('Windows Containers specific limits') where Windows-specific guidance is provided before any Linux-specific guidance. Additionally, Windows terminology (e.g., 'Windows Containers') is mentioned first, and Linux-specific continuous deployment network dependencies are only briefly referenced later. There are no PowerShell-only examples, and CLI examples use Azure CLI, which is cross-platform. Linux/macOS users can complete all tasks, but Windows-specific information is presented first.
Recommendations
- Ensure Linux container limits and guidance are described with equal prominence and detail as Windows containers.
- Present Linux and Windows-specific sections in parallel, or clarify when information is Windows-only.
- Add more explicit Linux/macOS examples or references where relevant (e.g., for environment variables, troubleshooting, or container networking).
- Consider including a summary table comparing Windows and Linux container subnet/IP requirements.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance via zone pivots, but Windows-specific examples, tools, and explanations are often presented first or in greater detail. PowerShell commands are included alongside Bash/Azure CLI, but Windows concepts (such as IIS, .NET Framework, and Windows Server images) receive more prominent coverage. Some sections (e.g., persistent storage, diagnostic logs, memory/core customization) default to Windows terminology and paths before Linux equivalents, and PowerShell is consistently shown as an alternative to Bash/CLI.
Recommendations
- Ensure Linux examples and terminology are presented with equal prominence and detail as Windows sections.
- Where possible, show Linux/Bash examples first or side-by-side with Windows/PowerShell to avoid implicit prioritization.
- Expand Linux-specific guidance (e.g., base images, troubleshooting, diagnostic logs) to match Windows coverage.
- Clarify when features or settings differ between Windows and Linux containers, and provide explicit Linux alternatives.
- Review for subtle language or ordering that may imply Windows is the default or preferred platform.
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 PowerShell examples for managing Key Vault permissions, but PowerShell is given equal prominence, and there are references to Windows-specific certificate tools (IIS, Certreq.exe) before Linux alternatives. Export instructions for certificates mention IIS and Certreq.exe for Windows, while OpenSSL is mentioned for Linux/macOS, but the Windows tools are listed first. The FAQ and automation sections also provide both CLI and PowerShell links, but PowerShell is listed second. Overall, there is a mild Windows-first and Windows tools bias, but Linux/macOS users are not blocked from completing any tasks.
Recommendations
- When listing certificate export options, present OpenSSL (cross-platform) instructions before Windows-specific tools like IIS or Certreq.exe.
- Explicitly mention that OpenSSL commands work on Linux/macOS and Windows (if OpenSSL is installed), and provide links to OpenSSL installation guides for Windows.
- Where PowerShell and CLI examples are given, consider listing Azure CLI (cross-platform) first.
- Add a brief note in relevant sections clarifying that all certificate management operations can be performed from Linux/macOS using Azure CLI and OpenSSL.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Patterns
Summary
The documentation is generally cross-platform, referencing both Windows and Linux app backup paths and Azure CLI usage (which is OS-agnostic). However, there are subtle Windows biases: Windows directory patterns (e.g., '%HOME%', 'D:\home\site\wwwroot') are mentioned first or exclusively in some places, and tools like Kudu DebugConsole and FTP are described using Windows-style paths. The instructions for creating the '_backup.filter' file use Windows directory notation and upload paths, with no explicit Linux path equivalents. The portal screenshots and instructions are platform-neutral, but the file system references and some terminology lean toward Windows conventions.
Recommendations
- Add explicit Linux path examples (e.g., '/home/site/wwwroot') alongside Windows paths when describing file locations and upload instructions.
- Clarify that Kudu DebugConsole and FTP can be used from any OS, and provide Linux/macOS command-line alternatives for file uploads (e.g., using SCP or Azure CLI).
- When referencing environment variables like '%HOME%', also mention the Linux equivalent ('$HOME').
- Ensure all directory/file instructions are given in both Windows and Linux formats.
- Consider showing Linux examples first or equally alongside Windows examples to reinforce 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
Powershell Heavy
Windows First
Summary
The documentation provides example commands for Azure portal, Azure CLI, and Azure PowerShell in all relevant sections. PowerShell examples are present throughout, and in some cases, PowerShell is listed before CLI in the metadata and custom tags. However, the CLI (which is cross-platform) is always present, and there are no steps that are Windows-only. There is a slight ordering bias in metadata and custom tags, and the inclusion of PowerShell in every example may signal a slight preference for Windows tooling, but Linux/macOS users are fully supported.
Recommendations
- Ensure that Azure CLI examples are always listed before or alongside PowerShell examples, especially in metadata and custom tags.
- Explicitly note that both Azure CLI and PowerShell are cross-platform, but CLI is often preferred for Linux/macOS users.
- Consider providing Bash shell scripting examples for common migration automation tasks to further improve Linux parity.
- In the documentation body, alternate the order of CLI and PowerShell tabs to avoid perceived preference.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is structured to provide parity between Windows and Linux custom container configuration in Azure App Service, using pivot sections for each OS. However, there are several areas where Windows examples, tools, and terminology are presented first or more prominently. PowerShell commands are frequently included alongside Bash/Azure CLI, and Windows-specific tools (like Kudu, IIS, .NET Framework, and Windows directory paths) are referenced before or more extensively than their Linux equivalents. Some sections (such as memory/core customization and persistent storage) show Windows details first, and troubleshooting/logging instructions often reference Windows-centric tools and paths.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally alternating or grouping by OS rather than always showing Windows first.
- Where PowerShell commands are given, ensure Bash/Azure CLI equivalents are equally detailed and not secondary.
- Expand Linux-specific troubleshooting/logging guidance to match the detail provided for Windows (e.g., Kudu, SSH, log access).
- Clarify Linux-specific directory paths and behaviors, avoiding references to Windows paths (e.g., C:\home) in Linux sections unless explicitly comparing.
- Where possible, provide Linux-first examples in sections that are not inherently Windows-centric.
- Review the use of Windows tools and terminology to ensure Linux users are not required to mentally translate instructions.
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 explicit OpenSSL (Linux/macOS) and Azure CLI examples. However, there are several instances where Windows-specific tools (IIS, Certreq.exe) are mentioned for certificate export, and PowerShell examples are provided alongside Azure CLI, sometimes with PowerShell shown first. Some links for certificate export reference Windows-only documentation. These patterns may create minor friction for Linux/macOS users, but workarounds and alternatives are present.
Recommendations
- Ensure that for every mention of Windows tools (IIS, Certreq.exe), equivalent Linux/macOS instructions or links are provided, not just OpenSSL.
- When referencing certificate export, link to cross-platform guides or add explicit Linux/macOS instructions, not just Windows Server documentation.
- Present Azure CLI examples before PowerShell, or clarify that both are supported equally.
- Review FAQ and related content to ensure parity in scripting and automation examples for Linux/macOS (e.g., Bash, Azure CLI).
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 step-by-step instructions and code examples for Azure portal, Azure CLI, and Azure PowerShell. PowerShell examples are present throughout, and in some sections, the PowerShell tab appears before or alongside CLI, which may suggest a slight preference for Windows tooling. However, all critical operations are fully covered with Azure CLI commands, ensuring Linux/macOS users can complete the migration. There are no Windows-only tools or patterns, and Linux is explicitly supported by the feature being documented.
Recommendations
- Ensure that Azure CLI examples are always presented before or at the same prominence as PowerShell examples, as CLI is cross-platform.
- Consider explicitly stating that all CLI commands are fully supported on Linux/macOS to reassure non-Windows users.
- If possible, add a brief note that PowerShell Core is available cross-platform, or clarify when examples are Windows PowerShell-specific.
- Continue to avoid using Windows-only tools or terminology in general-purpose networking documentation.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service plans for both Windows and Linux, mentioning both operating systems early and clarifying feature parity. However, the 'Managed Instance' section is Windows-only and is described before any Linux-specific advanced options, which may subtly prioritize Windows scenarios. No PowerShell-heavy or Windows tools bias is present, and Linux examples are not missing, but Windows-specific features are highlighted first in advanced hosting options.
Recommendations
- Add a comparable section for advanced Linux hosting options (if available), or clarify that Managed Instance is Windows-only and mention Linux alternatives if they exist.
- Ensure links and feature tables consistently reference both Windows and Linux plan details.
- Consider adding explicit Linux-specific guidance or examples where relevant, especially for scaling, pricing, and plan selection.
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 Azure CLI and Azure PowerShell examples for all procedural steps, with PowerShell examples present for every operation. While Azure CLI is cross-platform, the inclusion of PowerShell (which is historically Windows-centric, though now cross-platform) may still signal a Windows-first approach. In all code example tabs, PowerShell is always present, and in some cases, PowerShell appears before Bash or Linux-native alternatives. There are no Linux- or macOS-specific tools or shell scripts provided, and no explicit Bash examples are shown. However, the CLI examples do ensure Linux/macOS users can complete all tasks.
Recommendations
- Add explicit Bash shell examples (where applicable) alongside Azure CLI and PowerShell to demonstrate parity and comfort for Linux/macOS users.
- Clarify in the introduction that Azure CLI commands are fully supported on Linux/macOS, and that PowerShell Core is available cross-platform, to reduce perceived Windows bias.
- When listing code tabs, consider ordering as: Azure portal, Azure CLI, Bash (if applicable), then PowerShell, to avoid a Windows-first impression.
- Where PowerShell is used, note that PowerShell Core is available for Linux/macOS, or provide Bash equivalents for common scripting tasks.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, ARM templates, and portal instructions for most tasks. However, PowerShell examples are often shown alongside or before CLI examples, and PowerShell is referenced heavily. In some cases, PowerShell is used for both Windows and cross-platform scenarios, but the CLI examples (which are more universal for Linux/macOS) are not always given equal prominence. There are no Windows-only tools or patterns, but PowerShell is emphasized, which may create friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always shown before or alongside PowerShell examples, as CLI is cross-platform.
- Clarify that Azure PowerShell is available on Linux/macOS, but recommend Azure CLI for Linux/macOS users where possible.
- Add explicit notes or links for Linux/macOS users, especially where PowerShell is used, to highlight CLI alternatives.
- Where PowerShell is not supported (e.g., user-assigned identity for App Service), clarify alternatives 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 managing Key Vault permissions, but PowerShell is given equal prominence and is sometimes listed before Linux-native alternatives. There are references to Windows-specific tools (IIS, Certreq.exe) for certificate export, and the automation FAQ links to both PowerShell and CLI, but PowerShell is mentioned first. However, Linux tools (OpenSSL) are also referenced, and Azure CLI examples are present. Overall, the documentation is mostly cross-platform, but there is a slight Windows-first and PowerShell-heavy bias in some sections.
Recommendations
- When listing automation options, consistently present Azure CLI examples before PowerShell, as CLI is cross-platform.
- Where Windows-specific tools like IIS or Certreq.exe are mentioned, provide explicit Linux/macOS alternatives (e.g., OpenSSL commands) in parallel.
- In FAQ and automation sections, clarify which tools are cross-platform and recommend Azure CLI as the default for non-Windows users.
- Ensure screenshots and UI instructions do not assume a Windows environment unless necessary.