199
Pages Scanned
25
Pages Flagged
199
Changed Pages
12.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-06 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 199
Files Completed: 199
Problematic Pages
26 issues found
App Service
Tutorial: ASP.NET app with Azure SQL Database
...service/app-service-web-tutorial-dotnet-sqldatabase.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial is heavily oriented toward Windows users, specifically those using Visual Studio on Windows. All instructions, screenshots, and tooling references are for Visual Studio (Windows), with no mention of Linux/macOS alternatives. PowerShell and Package Manager Console commands are given, but no equivalent Bash or CLI instructions. The publishing workflow is tied to Visual Studio's Windows-centric features, and SQL Server Object Explorer is a Windows-only tool. There are no examples or guidance for Linux/macOS users, such as using VS Code, Azure CLI, or cross-platform deployment methods.
Recommendations
- Add instructions for Linux/macOS users, including how to use VS Code or the .NET CLI for project creation, running, and publishing.
- Provide Azure CLI or Bash equivalents for PowerShell commands, especially for database setup and migrations.
- Include cross-platform deployment options, such as using 'dotnet publish' and 'az webapp deploy'.
- Mention and show how to connect to Azure SQL Database using cross-platform tools (e.g., Azure Data Studio, sqlcmd on Linux/macOS).
- Clarify which steps are Windows-only and offer alternatives where possible.
Create Pull Request
API Management
Add a Custom CA Certificate - API Management | Microsoft Docs
...api-management/api-management-howto-ca-certificates.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides a PowerShell example (`New-AzApiManagementSystemCertificate`) for uploading a CA certificate but does not mention or provide equivalent CLI, Bash, or Linux/macOS tooling. The only command-line option is Windows-centric, and no Linux/macOS alternatives or parity are discussed.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform.
- Mention Bash or shell scripting alternatives if available.
- Clarify if the PowerShell command can be run on PowerShell Core (cross-platform) or if it is Windows-only.
- Provide guidance for Linux/macOS users, including any REST API or portal-based alternatives.
API Management
Defend API Management Against DDoS Attacks
...rticles/api-management/protect-with-ddos-protection.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation references enabling DDoS IP Protection via a linked PowerShell guide, without mentioning or linking to equivalent Azure CLI or Bash examples. The only explicit command-line example is PowerShell, and there is no mention of Linux/macOS-friendly tooling or instructions. The Azure portal steps are platform-neutral, but the command-line guidance is Windows-centric.
Recommendations
- Add Azure CLI examples for enabling DDoS IP Protection on public IP addresses, alongside PowerShell instructions.
- Explicitly mention that Azure CLI and Bash can be used on Linux/macOS for relevant operations.
- Link to cross-platform command-line documentation where possible, not only PowerShell guides.
- Ensure parity in example ordering (e.g., show Azure CLI first or alongside PowerShell).
App Service
Environment Variables and App Settings Reference
...ob/main/articles/app-service/reference-app-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation page covers environment variables and app settings for Azure App Service across both Windows and Linux platforms. However, there is a notable Windows bias: Windows-specific paths, tools, and terminology (such as IIS, msbuild, Web Deploy/MSDeploy, and Windows directory structures like D:\home) are referenced first or exclusively in several sections. Windows examples and settings often precede Linux equivalents, and some explanations default to Windows-centric language. Linux-specific details are present but sometimes secondary or less detailed.
Recommendations
- Ensure Linux paths and examples are provided alongside Windows ones, especially in introductory tables and explanations.
- When referencing tools (e.g., msbuild, Web Deploy), clarify Linux equivalents or alternatives (such as Oryx for build automation).
- Balance the order of presentation so Linux and Windows settings/examples are given equal prominence.
- Expand Linux-specific explanations where they are brief or missing, especially for deployment, logging, and build automation.
- Where possible, use platform-neutral language or clarify when a setting is platform-specific.
API Management
Use Managed Identities in Azure API Management | Microsoft Docs
...t/api-management-howto-use-managed-service-identity.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_first
Summary
The documentation provides detailed instructions and code samples for Azure portal, Azure PowerShell, and ARM templates, but omits equivalent examples for Linux/macOS users, such as Azure CLI. PowerShell is emphasized for scripting, and there are no references to cross-platform tools or shell environments. This creates friction for users on Linux or macOS, as they must adapt PowerShell commands or seek external resources.
Recommendations
- Add Azure CLI examples alongside PowerShell for all tasks, including creating and updating managed identities.
- Explicitly mention that Azure CLI is cross-platform and provide links to relevant CLI documentation.
- Ensure that scripting instructions are not PowerShell-exclusive, and clarify which tools are supported on Linux/macOS.
- Consider showing Azure CLI examples before or alongside PowerShell to emphasize platform neutrality.
App Service
Use TLS/SSL Certificates in App Code
...icles/app-service/configure-ssl-certificate-in-code.md
Medium Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific certificate store access is described in detail with C# and Java code samples, and the Windows workflow is presented first and most thoroughly. Linux examples are limited, only shown for C# in containers, and users of other languages (Node.js, PHP, Python, Java) are told to consult external documentation. Windows tools and patterns (certificate store, thumbprints, environment variables) are emphasized, and Linux equivalents are not given equal prominence or coverage.
Recommendations
- Add explicit Linux (and macOS, if relevant) code samples for popular languages (Node.js, Python, Java, PHP) showing how to load certificates from the file paths provided by App Service.
- Present Linux and Windows workflows in parallel or in clearly separated tabs, rather than focusing on Windows first.
- Include more discussion of Linux-specific certificate handling patterns, such as using OpenSSL or language-specific libraries to load .p12/.der files.
- Clarify any differences in certificate formats or handling between Windows and Linux environments.
- Where possible, provide direct code examples for Linux containers and apps, not just references to external documentation.
App Service
Install a TLS/SSL Certificate for Your App
...main/articles/app-service/configure-ssl-certificate.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
missing_linux_example
Summary
The documentation generally provides platform-agnostic guidance for managing TLS/SSL certificates in Azure App Service, but there are subtle Windows biases. When discussing exporting certificates, Windows tools (IIS, Certreq.exe) are mentioned explicitly, while Linux/macOS equivalents are not. PowerShell is given as an example for RBAC assignment, and the FAQ links to both Azure CLI and PowerShell, but the PowerShell script is listed second. There are no explicit Linux/macOS-specific instructions for certificate export or management, and no mention of common Linux certificate tools beyond OpenSSL.
Recommendations
- When referencing certificate export, provide explicit Linux/macOS guidance (e.g., using OpenSSL for all platforms, or mentioning 'certutil' for Linux).
- When mentioning Windows tools like IIS or Certreq.exe, also mention Linux/macOS equivalents or clarify that OpenSSL is cross-platform.
- For scripting examples (e.g., RBAC assignment), ensure both Azure CLI and PowerShell are presented in parallel, and clarify which is cross-platform.
- Add a short section or note clarifying that all certificate management steps (except those explicitly using Windows tools) can be performed on Linux/macOS using OpenSSL.
- In the FAQ and automation sections, ensure parity by listing Azure CLI and PowerShell examples together, and consider adding Bash or cross-platform scripting examples.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally platform-neutral, but the 'Hybrid Connections' section requires installation of Hybrid Connection Manager on Windows Server, with no mention of Linux/macOS alternatives. This creates friction for non-Windows users, as Linux-based relay agents or instructions are not provided. Other networking features are described in a cross-platform way, and no PowerShell or Windows-first examples are present.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux/macOS, and provide download links or instructions if so.
- If Linux/macOS support is unavailable, explicitly state this limitation and suggest alternative approaches for Linux users.
- Where possible, provide examples or guidance for configuring networking features from Linux/macOS environments (e.g., using Azure CLI, Bash, etc.).
- Review other sections for implicit Windows tool references and ensure parity in documentation for Linux/macOS users.
API Center
Quickstart - Create Your Azure API Center - Bicep
...ob/main/articles/api-center/set-up-api-center-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying Bicep files, but PowerShell is presented as a primary option alongside CLI. There is a slight bias in mentioning Azure PowerShell requirements and examples, which are more relevant to Windows users, and the PowerShell example is given equal prominence to the CLI example. However, Azure CLI is cross-platform and shown first, and all tasks can be completed on Linux/macOS using CLI.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes or callouts for Linux/macOS users, such as instructions for uploading files in Cloud Shell or using CLI locally.
- Consider mentioning that Azure PowerShell is available on Linux/macOS, but CLI is generally simpler for non-Windows environments.
- Ensure prerequisites and environment setup sections link to Linux/macOS-specific guidance where relevant.
API Management
Azure API Management virtual network injection - network resources
.../api-management/virtual-network-injection-resources.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts. However, in the 'Related content' section, a link to a PowerShell-based guide for connecting virtual networks is provided without mention of CLI or Linux-native alternatives. This subtly prioritizes Windows/PowerShell as the default automation tool, which may create friction for Linux/macOS users.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI or ARM template guides for connecting virtual networks, ensuring Linux/macOS users have clear, first-class options.
- Where PowerShell is referenced, clarify that equivalent steps can be performed using Azure CLI or provide links to those instructions.
- Review other cross-references to ensure that automation and scripting examples are not Windows/PowerShell-centric unless the feature is Windows-only.
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, ensuring cross-platform support. However, in each case, the PowerShell (Windows) example is shown after the Bash (Linux/macOS) example, which is the preferred order for neutrality. No exclusive Windows tools or patterns are used, and Linux users are not disadvantaged.
Recommendations
No significant changes are needed. The documentation already provides parity by including both Bash and PowerShell examples. Continue this approach for future updates.
API Management
Backup and restore your Azure API Management instance for disaster recovery
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/api-management/api-management-howto-disaster-recovery-backup-restore.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides comprehensive coverage for PowerShell (Windows-centric) usage, with detailed variable setup and command examples. While Azure CLI (cross-platform) and REST API examples are also included, PowerShell is consistently presented first and in greater detail, which may subtly prioritize Windows users. There are no Linux/macOS-specific issues, but the ordering and depth of PowerShell content reflect a mild Windows bias.
Recommendations
- Present Azure CLI (Bash) examples before or alongside PowerShell examples to emphasize cross-platform parity.
- Ensure that CLI examples are as detailed as PowerShell ones, including variable setup and context.
- Explicitly state that Azure CLI and REST API methods are fully supported on Linux/macOS.
- Consider adding a note that PowerShell Core is available cross-platform, if relevant, to clarify for non-Windows users.
API Management
Deploy a Self-Hosted Gateway to Azure Kubernetes Service
...to-deploy-self-hosted-gateway-azure-kubernetes-service.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation briefly mentions Azure PowerShell as an option for creating an AKS cluster before mentioning the Azure CLI and portal. However, all deployment and verification steps use kubectl commands, which are cross-platform and standard for Kubernetes. No PowerShell-specific commands or Windows-only tools are used in the main workflow.
Recommendations
- Consider listing Azure CLI before Azure PowerShell in the prerequisites, as CLI is more universally used across platforms.
- Explicitly note that all kubectl commands work equally on Windows, Linux, and macOS.
- If possible, provide links to Linux/macOS-specific installation guides for Azure CLI and kubectl.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are given for every step and are formatted with Windows-specific syntax. Bash examples are present, but PowerShell examples appear immediately after, suggesting parity but with a slight Windows-first bias. There are no missing Linux examples, but the PowerShell formatting and variable usage may create friction for Linux/macOS users.
Recommendations
- Ensure Bash examples are presented first or equally alongside PowerShell examples, especially since Azure CLI is cross-platform.
- Clarify that Bash examples are for Linux/macOS and PowerShell for Windows, to help users identify the relevant section.
- Consider providing a brief note about cross-platform compatibility and how to adapt examples for different shells.
- Review variable usage and syntax to ensure Bash examples are fully functional and not dependent on Windows-specific conventions.
API Center
Quickstart - Create Your Azure API Center - ARM Template
.../articles/api-center/set-up-api-center-arm-template.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying the ARM template. However, PowerShell is mentioned alongside CLI throughout, and the Azure PowerShell requirements are listed before the deployment section. The examples are presented in tabbed format, so Linux users can use Azure CLI, but PowerShell is a Windows-centric tool (though available cross-platform). There are no Linux-specific shell examples (e.g., Bash), and no explicit mention of Linux/macOS environments or tools.
Recommendations
- Add explicit Bash shell examples for ARM template deployment using Azure CLI.
- Clarify that Azure CLI works natively on Linux/macOS and Windows, and provide guidance for Linux/macOS users where relevant.
- Mention that PowerShell Core is cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
- Ensure prerequisites and environment setup instructions include Linux/macOS guidance (e.g., installation steps for Azure CLI on Linux).
API Management
Deploy an Azure API Management Instance to Multiple Azure Regions
...management/api-management-howto-deploy-multi-region.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation page provides instructions for deploying Azure API Management to multiple regions, primarily using the Azure portal and Azure CLI. The only explicit mention of a Windows-specific tool is the Azure PowerShell cmdlet (set-azapimanagement), which is listed after the Azure CLI and REST API options. No PowerShell-only examples are given, and the CLI is presented first. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. The only minor bias is listing PowerShell as an option, but this does not impact Linux/macOS users, as CLI and REST API alternatives are provided.
Recommendations
- Ensure that Azure CLI examples are always provided and shown before PowerShell examples.
- Clarify that Azure CLI and REST API are cross-platform and preferred for Linux/macOS users.
- If possible, provide Bash shell scripting examples for automation alongside CLI commands.
- Explicitly state that PowerShell is optional and not required for Linux/macOS users.
API Management
Import an OpenAPI specification to Azure API Management | Microsoft Docs
...ob/main/articles/api-management/import-api-from-oas.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion as a top-level example may create a Windows bias. The PowerShell example is given equal prominence to the CLI example, and there are no explicit Linux/macOS-specific instructions or troubleshooting tips. The CLI example is cross-platform, but PowerShell is presented as a standard workflow, which may confuse Linux/macOS users who typically use Bash or Zsh.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider adding Bash or shell script examples for Linux/macOS users, or explicitly state that Azure CLI is the preferred cross-platform tool.
- Add a note indicating that PowerShell can be used on Linux/macOS, but CLI is more common for those platforms.
- Ensure that CLI examples are shown first, or highlight their cross-platform nature.
API Management
Import SOAP API to Azure API Management | Microsoft Docs
...s/blob/main/articles/api-management/import-soap-api.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity between Azure CLI and Azure PowerShell examples for importing a SOAP API, but PowerShell is presented as a primary workflow alongside CLI. The prerequisites list both Azure CLI and Azure PowerShell, but does not mention Bash or shell scripting alternatives. The PowerShell example is given equal prominence to CLI, but PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users. However, the Azure CLI example is fully cross-platform and appears before PowerShell, mitigating the bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
- Add a note that Azure PowerShell is available on Linux/macOS, but CLI is generally preferred for non-Windows environments.
- Consider including Bash or shell scripting examples for common operations, or link to CLI scripting guides.
- Explicitly state that all tasks can be completed using Azure CLI on Linux/macOS.
API Management
Quickstart: Create Azure API Management instance by using Bicep
.../blob/main/articles/api-management/quickstart-bicep.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks. Azure CLI is cross-platform, while PowerShell is more commonly associated with Windows, though it is available on Linux/macOS. The CLI examples are consistently presented before PowerShell, and no Windows-specific tools or patterns are mentioned. No Linux/macOS-specific examples or shell scripts are provided, but the CLI coverage ensures Linux parity.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS as well as Windows.
- Consider adding brief notes or examples for Bash scripting or integrating Bicep deployments in Linux environments.
- Mention that PowerShell Core is available cross-platform, but CLI is generally preferred for Linux/macOS users.
App Service
Configure gateway-required virtual network integration for your app
...service/configure-gateway-required-vnet-integration.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation is for a feature (gateway-required virtual network integration) that is explicitly Windows-only, as stated in the content. However, troubleshooting and connectivity examples (e.g., Test-NetConnection PowerShell command, netstat -aon) are Windows-centric, and Linux equivalents are not provided. Windows tools and patterns are mentioned first and exclusively, which may create friction for Linux/macOS users who need to troubleshoot related networking issues in hybrid environments.
Recommendations
- Clarify early and prominently that gateway-required virtual network integration is Windows-only, which is already done, but also note that troubleshooting steps are Windows-centric.
- Where troubleshooting steps are given (e.g., Test-NetConnection, netstat -aon), provide equivalent Linux/macOS commands (e.g., nc, curl, netstat, ss) for users who may be working in mixed environments.
- Mention that Linux App Service users should use regional virtual network integration and link to relevant documentation.
- For tools like tcpping and nameresolver, specify if they are available on Linux/macOS or provide alternatives.
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides both Windows and Linux instructions using zone pivots, but in several shared sections, Windows/PowerShell examples are often presented before Linux/Bash equivalents. PowerShell commands are consistently included alongside Bash, and some sections (like persistent storage and memory/CPU settings) show Windows details or terminology first. There is also a slight emphasis on Windows tools and patterns (e.g., references to C:\home, IIS, .NET Framework, and Kudu) before their Linux alternatives, even in general sections.
Recommendations
- Where possible, alternate the order of Bash and PowerShell examples so Linux users see their platform first in some sections.
- Ensure that Linux-specific terminology (e.g., /home instead of C:\home) is used in Linux sections and not mixed with Windows paths.
- In shared sections, clarify when a feature or instruction is Windows- or Linux-specific, and avoid defaulting to Windows-first explanations.
- Consider adding more Linux-specific troubleshooting and diagnostic examples, similar to the detailed Kudu/PowerShell instructions for Windows.
- Review for any lingering references to Windows tools (e.g., IIS, .NET Framework) in general sections and move them to Windows-only pivots.
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.
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.