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 1901-1925 of 2121 flagged pages
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 as supported operating systems. However, the 'Managed Instance on Azure App Service' section is Windows-only and is described as such, which is appropriate given its feature scope. There are no command-line examples, tooling references, or patterns that favor Windows or PowerShell. The only minor bias is that Windows is sometimes mentioned first in lists and feature descriptions.
Recommendations
- Ensure that any future examples or walkthroughs include both Windows and Linux variants where applicable.
- If referencing tooling or scripts, provide both PowerShell and Bash/CLI equivalents.
- Clarify in introductory sections that Linux is equally supported for most App Service Plans, except where features are Windows-only.
Create Pull Request
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 prominent and often included even when Azure CLI covers the same scenario. In some sections, PowerShell is shown before CLI, and PowerShell-specific notes are present. However, the CLI examples are cross-platform and there are no Windows-only tools or patterns. No Linux/macOS-specific examples or notes are provided, but Linux users can complete all tasks using Azure CLI or ARM templates.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
- Add explicit notes clarifying that Azure CLI commands work on Linux/macOS and Windows.
- Where PowerShell is referenced, add a note that Azure CLI is recommended for Linux/macOS users.
- Consider including Bash shell examples for token retrieval (e.g., using curl) alongside PowerShell scripts.
- Add links or references to Linux/macOS-specific guidance where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation shows mild Windows bias. Windows file paths (%HOME%, D:\home\site\wwwroot) and Windows-centric terminology are used first or exclusively in several places. The Kudu DebugConsole and FTP upload instructions reference Windows-style paths and tools. While Azure CLI is presented as the primary cross-platform automation method, Azure PowerShell is also mentioned, but no Linux/macOS shell examples (e.g., Bash) or Linux-specific file paths are provided. The documentation does note Linux app backup locations (/home), but overall, Windows patterns and tools are more prominent.
Recommendations
- Add Linux/macOS file path examples (e.g., /home/site/wwwroot) alongside Windows paths in sections about backup filters and file uploads.
- Clarify that Kudu DebugConsole and FTP can be used from any OS, and provide instructions for Linux/macOS users (e.g., using sftp or scp).
- Include Bash shell script samples for backup automation, not just Azure CLI and PowerShell.
- Where file paths are referenced, show both Windows and Linux formats.
- Ensure screenshots and UI references are not Windows-only if the portal experience is 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
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 presented alongside Azure CLI, but are shown after CLI examples. There is no evidence of exclusive Windows tools or patterns, and Linux parity is maintained via Azure CLI examples. However, the presence of Azure PowerShell examples (which are Windows-centric) may suggest a mild Windows bias, especially since PowerShell is less commonly used on Linux/macOS. The documentation does not provide Bash or shell script examples, but Azure CLI is cross-platform and sufficient for Linux/macOS users.
Recommendations
- Consider clarifying that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Add brief notes or links for Linux/macOS users indicating that Azure CLI is fully supported and preferred for cross-platform scenarios.
- Optionally, provide Bash or shell script examples for common tasks to further improve Linux parity.
- Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
App Service
Authentication and Authorization
...s/app-service/overview-authentication-authorization.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation describes both Windows and Linux/container architectures for the authentication module, but the Windows (IIS module) explanation is presented first and in slightly greater detail. All command-line examples use cross-platform Azure CLI (az), and no Windows-only tools or PowerShell are referenced. There are no missing Linux examples, and Linux/container deployment is explicitly covered. The only minor bias is the ordering of Windows before Linux in the architecture section.
Recommendations
- Present Linux/container architecture before or alongside Windows to avoid implicit prioritization.
- Ensure parity in detail and clarity between Windows and Linux/container explanations.
- Continue using cross-platform tools (Azure CLI) for examples and avoid Windows-only tooling unless necessary.
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 several shared sections, Windows/PowerShell examples are consistently presented before Linux/Bash equivalents. PowerShell commands are included alongside Bash for most configuration steps, and some advanced configuration and troubleshooting (e.g., customizing container memory, CPU, health ping, and diagnostic log access) are described in more detail for Windows containers. Windows-specific tools and patterns (e.g., C:\home, System.ConfigurationManager, IIS, .NET Framework) are referenced more prominently, and some sections (like customizing ASP.NET machine key injection) are Windows-only. However, Linux parity is generally maintained through dedicated pivot sections and Linux-specific instructions.
Recommendations
- When providing both Bash and PowerShell examples, alternate the order or clearly label both as equal options to avoid implicit prioritization.
- Ensure that advanced configuration and troubleshooting sections for Linux containers are as detailed as those for Windows containers, especially for topics like diagnostic log access, resource limits, and health checks.
- Where possible, provide Linux-native tool references (e.g., mention /home before C:\home in shared sections) and avoid defaulting to Windows terminology in cross-platform sections.
- Review pivoted content to ensure Linux and Windows sections are equally comprehensive and up-to-date.
- Consider adding a summary table at the top outlining which features/commands apply to Windows, Linux, or both, to help users quickly find relevant instructions.
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 associated with Windows environments, and its examples are given equal prominence alongside CLI. The ordering of examples consistently places Azure PowerShell after CLI, but before any mention of Linux-specific tooling. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not reference Linux tools or patterns. However, the CLI examples are sufficient for Linux/macOS users, and the documentation does not require Windows-only tools for any critical steps.
Recommendations
- Explicitly state that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform automation tool.
- Consider adding Bash shell script examples or clarifying that CLI commands are suitable for Linux/macOS users.
- If PowerShell is included, note that PowerShell Core is available cross-platform, but CLI is generally preferred for Linux users.
- Review ordering of examples to ensure CLI (cross-platform) is shown before PowerShell, and clarify tool suitability for each OS.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service plans, covering both Windows and Linux options. However, in the 'Managed Instance on Azure App Service (preview)' section, Windows-specific features and tools (such as PowerShell, RDP, IIS customization, .NET Framework) are discussed first and in detail, with explicit mention that this feature is Windows-only. While this is accurate and appropriate for the feature, the overall page does not provide Linux-specific examples or parity for similar advanced hosting scenarios, and Windows terminology appears before Linux in some places.
Recommendations
- Add Linux-specific advanced hosting options or clarify their absence, especially for scenarios like OS customization, private networking, and legacy component support.
- When listing operating systems or features, alternate the order or explicitly state Linux capabilities where relevant.
- Provide links or references to Linux hosting documentation for users seeking similar functionality.
- Ensure parity in examples and explanations for scaling, pricing, and feature availability between Windows and Linux where applicable.
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
Missing Linux Example
Summary
The documentation generally aims for cross-platform parity, but there are subtle Windows biases. In the 'Export the merged private certificate to .pfx' section, explicit instructions are provided for both OpenSSL (Linux/macOS) and Windows tools (IIS, Certreq.exe). However, the Windows export path is referenced with a link to a Windows Server 2008-era guide, and no equivalent Linux/macOS GUI or alternative is mentioned. In the FAQ and automation sections, both Azure CLI (cross-platform) and Azure PowerShell (primarily Windows, but available cross-platform) are referenced, but PowerShell is mentioned second. The only significant bias is that Windows tools are referenced for certificate export without Linux GUI alternatives, and the documentation does not clarify that all steps are equally supported on Linux/macOS. There are no PowerShell-heavy or Windows-only sections, but minor friction exists for Linux/macOS users.
Recommendations
- Add explicit notes confirming that all certificate management steps (including .pfx export and upload) are fully supported on Linux/macOS.
- Provide a Linux/macOS GUI alternative (such as using GNOME Certificates or Keychain Access) for exporting .pfx files, or clarify that OpenSSL is the recommended tool for non-Windows users.
- Update the Windows export link to a more current version if possible, and consider adding a Linux/macOS-focused quickstart for certificate export.
- Where Windows tools are mentioned (IIS, Certreq.exe), add a parallel note or link for Linux/macOS users to avoid the impression of Windows-first support.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, ARM templates, and portal instructions for most tasks. However, PowerShell examples are prominent and often shown alongside or before CLI examples, and PowerShell is referenced in several places (including a dedicated 'PowerShell' tab for token retrieval). Azure PowerShell is a cross-platform tool, but its historical association with Windows and the presence of a dedicated PowerShell tab (in addition to Azure CLI) may create a perception of Windows bias. The CLI examples are present and correct, but PowerShell is sometimes prioritized or referenced first. There are no outright missing Linux examples, and no exclusive mention of Windows-only tools.
Recommendations
- Ensure Azure CLI examples are always presented before or alongside PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Clarify that Azure PowerShell is cross-platform and not Windows-only, to avoid confusion.
- Consider adding Bash shell script examples for token retrieval, especially in the 'Connect to Azure services in app code' section, to further improve Linux parity.
- Review tab ordering and ensure CLI is not deprioritized compared to PowerShell.
- Explicitly mention that all instructions (except PowerShell tab) are applicable to Linux/macOS unless otherwise noted.
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 largely platform-neutral, focusing on Azure App Service virtual network integration. However, there is a section ('Windows Containers specific limits') where Windows container-specific guidance and calculations are presented before any Linux-specific information. Linux container guidance is only mentioned briefly in the 'Linux continuous deployment' subsection, which is much shorter and less detailed. There are no PowerShell-only examples, Windows tools, or missing Linux examples for core tasks, but Windows-specific guidance appears first and is more detailed.
Recommendations
- Add a comparable section for Linux containers, including subnet sizing, IP address requirements, and networking unit calculations, to match the detail provided for Windows containers.
- Ensure Linux-specific guidance is as prominent and detailed as Windows guidance, especially in sections about container limits and networking.
- Consider presenting Linux and Windows container guidance side-by-side or in parallel subsections for parity.
- Expand the 'Linux continuous deployment' section to include more details, such as subnet/IP requirements, limitations, and troubleshooting tips.
App Service
Tutorial: Access Azure databases with managed identity
...les/app-service/tutorial-connect-msi-azure-database.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally provides cross-platform guidance, using Azure CLI and mentioning development environments for Windows, macOS, and Linux. However, there is a minor Windows-first bias in the 'Set up your dev environment' section, where Visual Studio for Windows is described first and in more detail, while Visual Studio for Mac and Linux users are directed to use Azure CLI. PowerShell is also mentioned as an option, but not prioritized. All critical tasks can be completed on Linux/macOS, but the ordering and emphasis slightly favor Windows.
Recommendations
- Reorder the 'Set up your dev environment' tabs so that cross-platform tools (Azure CLI, Visual Studio Code) are listed before Windows-specific tools (Visual Studio for Windows, PowerShell).
- Explicitly mention Linux as a supported development environment in the prerequisites and dev environment setup.
- Provide parity in instructions and detail for macOS/Linux users, especially for Visual Studio Code and Azure CLI.
- Where possible, avoid language that implies Visual Studio for Windows is the default or primary workflow.
- Ensure all code and CLI examples are clearly marked as cross-platform, and clarify any Windows-only steps.
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/general sections, Windows/PowerShell examples are often shown before Linux/Bash equivalents. PowerShell commands are consistently included alongside Bash, and some sections (like persistent storage and environment variables) mention Windows paths or behaviors first. There is also a tendency to reference Windows-specific tools and concepts (e.g., C:\home, IIS, .NET Framework) before their Linux counterparts, even in general guidance. However, Linux content is present and substantial, and Linux-specific instructions (e.g., for SSH, Docker Compose) are included where relevant.
Recommendations
- In shared/general sections, alternate the order of Bash and PowerShell examples, or present Bash (Linux/macOS) first to avoid implicit prioritization of Windows.
- Where possible, use neutral language and paths (e.g., '/home' and 'C:\home') together, or clarify platform-specific differences up front.
- Ensure that Linux-specific tools and workflows are mentioned with equal prominence and detail as Windows tools.
- Consider adding a summary table or section at the top that clearly distinguishes which instructions are for Windows and which are for Linux, to help users quickly find relevant content.
- Review for any subtle language that assumes a Windows-first audience (e.g., referencing Windows paths or features before Linux) and balance with Linux equivalents.
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 presented alongside CLI examples. In several sections, PowerShell examples are shown after CLI but are always present, which may reinforce Windows-centric workflows. There is no evidence of missing Linux/macOS examples, and the documentation does not reference Windows-specific tools or patterns outside PowerShell. The overall structure is platform-neutral, but the inclusion of PowerShell in every example may create a subtle Windows bias.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Consider explicitly mentioning that Azure CLI is recommended for Linux/macOS users.
- If possible, add brief notes or links for Bash scripting or automation for Linux users.
- Ensure that CLI examples are shown first or highlighted as the default for cross-platform scenarios.
- Review whether PowerShell examples are necessary in every section, or if they can be grouped in a dedicated appendix.
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 Windows biases: Windows path patterns (e.g., `%HOME%`, `D:\home\site\wwwroot\`), references to Kudu DebugConsole (which is more familiar to Windows users), and the use of Windows-style paths in backup filter examples. PowerShell is mentioned alongside Azure CLI for scripting, but no Bash or Linux shell scripting samples are linked. Windows path conventions and terminology are often presented first or exclusively, with Linux equivalents only briefly mentioned.
Recommendations
- Add explicit Linux/macOS path examples (e.g., `/home/site/wwwroot/`) alongside Windows paths.
- Provide Bash/Linux shell scripting samples in the 'Automate with scripts' section, not just PowerShell.
- Clarify that Kudu DebugConsole is available for both Windows and Linux App Service apps.
- Where `%HOME%` is referenced, add a note that Linux apps use `/home`.
- In backup filter examples, show both Windows and Linux path formats.
- Ensure that instructions for uploading files (e.g., via FTP) mention Linux-compatible tools and paths.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of Azure App Service Plans, explicitly noting 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, IIS customization, .NET Framework) are described first and in detail, while Linux is only mentioned as unsupported for this feature. The main content otherwise avoids Windows bias, but the Windows-focused Managed Instance section appears before any Linux equivalent (which does not exist), potentially giving Windows users more visibility.
Recommendations
- Clearly label Windows-only features (such as Managed Instance) as Windows-specific, and consider grouping them in a dedicated section to avoid confusion.
- If Linux equivalents exist (e.g., Linux containers, custom OS features), provide links or brief descriptions for Linux users.
- Ensure parity in examples and guidance for both Windows and Linux App Service plans throughout the documentation.
- Add a short note in the Managed Instance section clarifying that Linux users should use standard App Service plans or containers for OS customization.
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 examples for Azure portal, Azure CLI, and Azure PowerShell in all relevant sections. However, PowerShell examples are always present and shown alongside CLI, which may subtly prioritize Windows users. The ordering of examples (portal, CLI, then PowerShell) is consistent, but PowerShell is included even though it is primarily a Windows tool, while no Linux/macOS-specific shell examples (e.g., Bash, zsh) are given. There is no evidence of Windows-only tools or patterns, and Linux parity is generally maintained, but the presence and prominence of PowerShell may create minor friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, not just Windows.
- Consider adding Bash/zsh script examples where appropriate, or explicitly state that Azure CLI commands are suitable for Linux/macOS users.
- If PowerShell is included, note its availability on non-Windows platforms to avoid implicit Windows bias.
- Ensure that CLI examples are equally prominent and that Linux/macOS users are not left uncertain about tool compatibility.
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 platform architecture details for both Windows (IIS module) and Linux/containers (Ambassador pattern), but the Windows section is presented first and slightly more detailed. All command-line examples use cross-platform Azure CLI (az), and no Windows-specific tools or PowerShell are mentioned. No critical features are described as Windows-only, and Linux/container parity is generally maintained.
Recommendations
- Consider presenting Linux/container architecture details before or alongside Windows to avoid implicit Windows-first bias.
- Explicitly state that all Azure CLI examples are cross-platform and work on Linux/macOS as well as Windows.
- If possible, add clarifying notes about any minor differences in configuration or troubleshooting on Linux/container platforms.
- Ensure parity in troubleshooting/logging guidance for Linux/container environments, if any platform-specific differences exist.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides cross-platform instructions for managing identities in Azure App Service and Azure Functions, including Azure CLI, PowerShell, ARM templates, and SDKs for .NET, JavaScript, Python, and Java. However, PowerShell examples are prominent and often listed before Azure CLI, and PowerShell is referenced heavily in some sections. Azure CLI (which is cross-platform) is included, but PowerShell (traditionally Windows-centric) is sometimes prioritized, and there are minor instances where PowerShell is used for tasks that could be shown with Bash or other Linux-native tools. There are no outright missing Linux examples, but the ordering and prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
- Where possible, add Bash shell script examples alongside PowerShell for token retrieval and scripting.
- Clarify that Azure PowerShell is available cross-platform, but highlight Azure CLI as the preferred tool for Linux/macOS users.
- Consider including explicit notes or links for Linux/macOS users regarding installation and usage of Azure CLI and Azure PowerShell.
- Review and balance example ordering so that Windows-specific tools (PowerShell) do not appear before cross-platform tools (CLI/ARM).
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 comprehensive overview of Azure App Service virtual network integration, with most content applicable to both Windows and Linux. However, in the 'Subnet requirements' section, Windows Containers-specific limits and calculations are described before any Linux-specific guidance. There are also more detailed examples for Windows Containers, while Linux container guidance is less prominent and only briefly mentioned in the 'Linux continuous deployment' section.
Recommendations
- Add parity by including Linux container-specific subnet/IP guidance alongside Windows Containers, not only in the Linux continuous deployment section.
- Ensure Linux-specific examples and limits are described with equal detail and visibility as Windows equivalents.
- Where Windows-specific guidance is given, provide a clear Linux counterpart or clarify if not applicable.
- Consider reorganizing sections so Linux and Windows guidance are presented together, rather than Windows first.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Paths
Summary
The documentation provides both Azure portal and Azure CLI instructions, which are cross-platform. However, there are several subtle Windows biases: Windows file 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 Windows-centric. Azure PowerShell is mentioned alongside Azure CLI for automation, but no Linux/macOS shell scripting examples are given. Windows paths and terminology appear before Linux equivalents in some tables and explanations.
Recommendations
- Add Linux/macOS file path examples (e.g., /home/site/wwwroot) alongside Windows paths wherever file operations are described.
- Clarify that Kudu DebugConsole and FTP methods are available for both Windows and Linux apps, and provide instructions for Linux users where relevant.
- Provide bash shell scripting samples for backup automation, not just Azure CLI and PowerShell.
- In tables and explanations, list Linux and Windows paths/environments equally, not always Windows first.
- Explicitly note any differences in backup behavior or file access between Windows and Linux App Service plans.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally provides parity between Windows and Linux custom container configuration for Azure App Service, using clear pivot sections for each OS. However, there are several areas where Windows examples, tools, or concepts are presented first or in greater detail, and PowerShell commands are often included alongside Bash, sometimes with more explanation. Some sections (e.g., persistent storage, environment variables, and app settings) show Windows commands or concepts before Linux equivalents, and Windows-specific tools (like Kudu) are referenced more frequently. However, Linux-specific instructions (e.g., for SSH, Docker Compose) are also present and detailed.
Recommendations
- Ensure that Linux and Windows instructions/examples are always presented with equal prominence and detail, ideally side-by-side or with clear pivots.
- Where both Bash and PowerShell commands are provided, ensure explanations are equally detailed for both, and that Linux/Bash is not always shown second.
- When referencing platform tools (e.g., Kudu, Azure portal), clarify their availability and usage for both Windows and Linux containers.
- In sections where only Windows-specific features are relevant (e.g., IIS, .NET Framework), clearly label them as such to avoid confusion.
- Review the order of sections to avoid consistently presenting Windows-first, unless there is a technical reason.
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 throughout migration steps. Azure PowerShell examples are consistently included alongside CLI and portal, and are shown immediately after CLI examples. While PowerShell is not strictly Windows-only (it is cross-platform), its usage is most common on Windows, and its inclusion alongside CLI may subtly prioritize Windows users. However, Linux users are fully supported via Azure CLI and portal instructions, and all migration steps can be completed on Linux/macOS. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained.
Recommendations
- Consider listing Azure CLI examples before PowerShell, as CLI is natively cross-platform and more common for Linux/macOS users.
- Explicitly note that Azure PowerShell is available cross-platform to avoid perception of Windows bias.
- If possible, add brief notes or links for Bash scripting or automation for Linux users, though Azure CLI coverage is sufficient.
- Maintain parity by ensuring all steps have CLI and portal instructions.
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, Windows (IIS module) is described first, followed by Linux/containers. All CLI examples use Azure CLI, which is cross-platform, and no PowerShell or Windows-only tools are referenced. No Windows-specific patterns or tools are prioritized, and Linux parity is generally maintained.
Recommendations
- Consider presenting Linux/container architecture before Windows to avoid subtle ordering bias.
- Explicitly confirm that all CLI commands work on Linux/macOS as well as Windows.
- If possible, add a brief note clarifying that authentication features are available and supported equally on both Windows and Linux App Service plans.
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, but PowerShell examples are prominent and often shown before CLI equivalents. In several sections, PowerShell is presented as a primary scripting option, and some code blocks (especially for user-assigned identities) are PowerShell-heavy. However, Azure CLI examples are also included, and the CLI is cross-platform. No Windows-only tools or patterns are referenced, and Linux users can complete all tasks using CLI or ARM templates. Minor bias is present in the ordering and prominence of PowerShell.
Recommendations
- Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
- Clarify that Azure PowerShell is available on Linux/macOS, but CLI is often preferred for cross-platform scripting.
- Add Bash shell script examples where appropriate, especially for token retrieval.
- Explicitly mention that all CLI and ARM template steps work on Linux/macOS.
- Consider adding a note about PowerShell Core availability on Linux/macOS for completeness.