220
Pages Scanned
31
Pages Flagged
220
Changed Pages
14.1%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-02 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure
Current Phase: discovery
Files Queued: 220
Files Completed: 220
Problematic Pages
33 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
windows_first
missing_linux_example
powershell_heavy
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 cross-platform alternatives such as Visual Studio Code, CLI tools, or Linux/macOS workflows. PowerShell and Windows-specific tools (e.g., Package Manager Console, SQL Server Object Explorer) are used exclusively, and Linux/macOS users are not provided with equivalent guidance or examples.
Recommendations
- Add instructions for deploying ASP.NET Core apps using Visual Studio Code or the .NET CLI, which are cross-platform.
- Provide examples for connecting to Azure SQL Database using sqlcmd or Azure CLI on Linux/macOS.
- Include guidance for package management and migrations using the dotnet CLI instead of Visual Studio's Package Manager Console.
- Mention and show how to use cross-platform editors and tools (e.g., VS Code, Azure Data Studio) for database management.
- Clarify which steps are Windows-only and provide Linux/macOS alternatives where possible.
Create Pull Request
Application Gateway
Tutorial: Configure an Application Gateway with TLS termination using the Azure portal
...main/articles/application-gateway/create-ssl-portal.md
High Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial demonstrates significant Windows bias by exclusively using Windows PowerShell commands for certificate creation and VM configuration, referencing Windows-specific tools (New-SelfSignedCertificate, Export-PfxCertificate), and only providing instructions for deploying Windows Server VMs and IIS. No Linux/macOS equivalents or alternatives are offered for certificate creation, VM setup, or backend testing.
Recommendations
- Add Linux/macOS instructions for creating a self-signed certificate (e.g., using OpenSSL) and exporting to PFX format.
- Provide examples for deploying Linux VMs as backend servers, including steps for installing a web server (e.g., Apache or Nginx) for testing.
- Include Azure CLI or Bash Cloud Shell alternatives for VM extension installation and configuration.
- Clearly indicate that both Windows and Linux backend pools are supported, and provide parity in examples.
Application Gateway
Deploy Application Gateway Basic (Preview)
...in/articles/application-gateway/deploy-basic-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates notable Windows bias. Azure PowerShell is used exclusively for preview registration and IIS installation, with no equivalent Bash/CLI or Linux examples. The VM creation section defaults to Windows Server, and IIS is used for backend testing, omitting Linux VM or Apache/Nginx alternatives. Linux users must adapt steps without guidance.
Recommendations
- Provide Azure CLI (Bash) commands for preview registration/unregistration alongside PowerShell.
- Include Linux VM creation steps (e.g., Ubuntu) as backend pool alternatives.
- Offer instructions for installing Apache or Nginx on Linux VMs for backend testing.
- Show both Windows and Linux examples for backend pool configuration.
- Clarify that backend VMs can be Linux and link to relevant Linux documentation.
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 command (`New-AzApiManagementSystemCertificate`) as the only CLI example for uploading a CA certificate, without mentioning or providing equivalent Azure CLI or REST API instructions. This creates friction for Linux/macOS users, as PowerShell is primarily a Windows tool and not always available or preferred on other platforms.
Recommendations
- Add Azure CLI examples for uploading CA certificates, as Azure CLI is cross-platform and widely used.
- Mention REST API options for certificate upload, with example requests.
- Clarify that PowerShell is optional and provide links or instructions for installing PowerShell on Linux/macOS if needed.
- Ensure that all CLI instructions are presented in a platform-neutral way, or at least offer parity 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
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure CLI, and Azure PowerShell. PowerShell examples are included alongside CLI, but PowerShell is a Windows-centric tool and is presented as a primary workflow. The prerequisites list Azure CLI and Azure PowerShell separately, but does not clarify that PowerShell is Windows-focused or offer Linux/macOS alternatives (e.g., Bash, shell scripting). The CLI example is cross-platform, but PowerShell is not. The order of examples (portal, CLI, PowerShell) is reasonable, but the inclusion of PowerShell as a main workflow may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users; suggest CLI for Linux/macOS.
- Consider adding Bash or shell script examples for Linux users, or explicitly state that Azure CLI is the recommended cross-platform tool.
- Add a note in the prerequisites section indicating that Azure PowerShell is Windows-centric and that Linux/macOS users should use Azure CLI.
- If possible, provide links to Azure CLI installation and usage guides for Linux/macOS.
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_tools
Summary
The documentation provides step-by-step instructions and code samples for creating and managing managed identities in Azure API Management using the Azure portal, Azure PowerShell, and ARM templates. However, it exclusively features Azure PowerShell for CLI-based examples, with no mention of Azure CLI (cross-platform) or Bash scripting. Instructions for installing Azure PowerShell reference Windows-centric tools and patterns, and there are no Linux/macOS-specific examples or guidance. This creates friction for Linux/macOS users who typically use Azure CLI or Bash.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell code samples, including resource group creation, API Management instance creation, and identity assignment.
- Include instructions for installing and using Azure CLI on Linux/macOS, alongside PowerShell guidance.
- Mention that Azure CLI is a cross-platform alternative and provide links to relevant Azure CLI documentation.
- Where possible, provide Bash script examples for ARM template deployments.
- Ensure that references to 'PowerShell samples' are accompanied by 'Azure CLI samples' or links to CLI documentation.
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
missing_linux_example
windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific certificate store access is covered in detail with C# and Java examples, while Linux guidance is limited to C# file loading and lacks parity for other languages. Windows tools and patterns (certificate store, thumbprint access) are emphasized first and more thoroughly. Linux examples for Node.js, PHP, Python, and Java are missing, and users are referred to external documentation. Windows-specific environment variables and certificate store details are prominent, while Linux guidance is less comprehensive.
Recommendations
- Add Linux-specific code examples for Node.js, PHP, Python, and Java, showing how to load certificates from file paths.
- Present Linux and Windows guidance in parallel sections, rather than Windows-first.
- Expand Linux container documentation to include environment variable usage and certificate loading patterns for multiple languages.
- Clarify differences between Windows and Linux certificate handling earlier in the article.
- Provide links or snippets for Linux language documentation where external guidance is referenced.
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
powershell_heavy
Summary
The documentation generally provides cross-platform guidance for managing TLS/SSL certificates in Azure App Service, with a strong focus on Azure Portal and Azure CLI. However, there are several instances where Windows tools (IIS, Certreq.exe) are referenced for certificate export, and PowerShell examples are given alongside Azure CLI. In some cases, Windows tools are mentioned before Linux alternatives, and PowerShell is presented as a primary automation option. While Linux users can complete all tasks (notably with OpenSSL and Azure CLI), the documentation could better highlight Linux/macOS parity and alternatives.
Recommendations
- When referencing certificate export tools, mention Linux/macOS alternatives (such as OpenSSL) before or alongside Windows tools like IIS or Certreq.exe.
- Ensure all automation examples (e.g., for RBAC/Key Vault permissions) provide Azure CLI as the primary or first option, with PowerShell as an alternative.
- Wherever PowerShell is shown, explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes or callouts for Linux/macOS users in sections that reference Windows-specific tools.
- Consider adding a table or section summarizing certificate generation/export steps for both Windows and Linux/macOS environments.
Medium Priority
View Details â
Detected Bias Types
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform and focuses on Azure App Service networking features, which are available for both Windows and Linux hosted apps. However, the 'Hybrid Connections' section exclusively mentions installing the Hybrid Connection Manager on Windows Server 2012 or newer, with no mention of Linux support or alternatives. There are no PowerShell-heavy examples or Windows-first ordering, but the omission of Linux instructions for Hybrid Connections creates friction for Linux users.
Recommendations
- Clarify whether Hybrid Connection Manager is available for Linux hosts, and if so, provide installation instructions or links for Linux.
- If Hybrid Connection Manager is Windows-only, explicitly state this limitation and suggest alternatives for Linux users.
- Review other sections to ensure any tool or feature that has platform-specific requirements is clearly documented for both Windows and Linux.
- Where possible, provide parity in examples and instructions for both Windows and Linux environments.
Application Gateway
Scaling and Zone-redundant Application Gateway v2
...eway/application-gateway-autoscaling-zone-redundant.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page is generally platform-neutral in its conceptual explanations, but the 'Next steps' section highlights Azure PowerShell as the primary tool for creating an autoscaling, zone-redundant Application Gateway. No equivalent Linux/macOS CLI (Azure CLI or ARM template) example or tutorial is referenced, and PowerShell is mentioned before any other tooling.
Recommendations
- Add links or references to Azure CLI tutorials for creating autoscaling, zone-redundant Application Gateways.
- Include ARM template or Bicep deployment examples for cross-platform parity.
- Mention Azure CLI alongside PowerShell in the 'Next steps' section to guide Linux/macOS users.
- Ensure that future tutorials and examples are available for both PowerShell and Azure CLI.
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation page provides detailed guidance for enabling diagnostic logging on Azure Application Gateway, but only includes PowerShell examples for command-line configuration. There are no equivalent CLI or Bash examples for Linux/macOS users. Additionally, references to log conversion tools are Windows-centric (Visual Studio, C#), and data visualization recommendations focus on Excel and Power BI, which are more commonly used on Windows. No Linux-specific tools or workflows are mentioned.
Recommendations
- Add Azure CLI and/or Bash examples alongside PowerShell for enabling diagnostic logging.
- Mention cross-platform log conversion tools (e.g., Python scripts, jq) for processing JSON logs.
- Include references to Linux/macOS-friendly data visualization tools (e.g., Grafana, Kibana) in addition to Excel and Power BI.
- Ensure that instructions for retrieving resource IDs and configuring diagnostic settings are platform-neutral or provide alternatives for Linux/macOS users.
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
missing_linux_example
Summary
The documentation generally covers both Windows and Linux App Service environments, but there is a consistent pattern of mentioning Windows paths, tools, and behaviors first or exclusively in some sections. Several environment variable descriptions provide Windows-centric examples (e.g., paths like D:\home), reference Windows tools (like msbuild, Web Deploy/MSDeploy, applicationHost.config), and sometimes omit equivalent Linux examples or details. However, Linux is also covered in most sections, and there are Linux-specific variables and notes. The bias is moderate: Linux users can complete tasks, but may experience friction due to Windows-first presentation and lack of parity in some explanations.
Recommendations
- When providing path examples, always show both Windows and Linux equivalents (e.g., D:\home and /home).
- For variables or features that behave differently on Windows and Linux, clearly document both behaviors and provide examples for each.
- Avoid referencing Windows tools (e.g., msbuild, Web Deploy) without mentioning Linux alternatives or clarifying their applicability.
- In tables and lists, alternate or parallelize Windows and Linux information rather than consistently listing Windows first.
- Where features are Windows-only, explicitly state this to avoid confusion.
- Expand Linux-specific sections (e.g., Oryx build automation) to match the detail level of Windows (Kudu) sections.
Application Gateway
Health monitoring overview for Azure Application Gateway
...lication-gateway/application-gateway-probe-overview.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page provides PowerShell-centric examples for configuring custom health probe match criteria, specifically referencing the New-AzApplicationGatewayProbeHealthResponseMatch cmdlet. The MinServers property is described as only configurable via PowerShell, Azure CLI, or ARM templates, but the example and guidance focus on PowerShell. Additionally, PowerShell is mentioned before Azure CLI or ARM templates, and the 'devx-track-azurepowershell' custom tag suggests a Windows/PowerShell-first approach. There are no explicit Linux/CLI examples, and the 'Next steps' section links to a PowerShell guide before mentioning the Azure portal.
Recommendations
- Add equivalent Azure CLI examples for probe configuration and match criteria, especially for Linux/macOS users.
- Explicitly mention ARM template and REST API options where applicable, with links or examples.
- Ensure 'Next steps' includes links to CLI and ARM template guides alongside PowerShell and portal.
- Balance PowerShell and CLI coverage in examples and explanations.
- Consider a section highlighting cross-platform management options for Application Gateway.
Application Gateway
Tutorial: Create and configure an application gateway to host multiple web sites using the Azure portal
...es/application-gateway/create-multiple-sites-portal.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
windows_tools
Summary
The tutorial demonstrates notable Windows bias: backend VM creation is only shown for Windows Server, IIS installation uses PowerShell, and hosts file editing is described exclusively for Windows (with DOS commands and Windows file paths). No Linux/macOS equivalents are provided for VM creation, web server setup, or hosts file editing, making the experience less accessible for non-Windows users.
Recommendations
- Add instructions for creating Linux VMs (e.g., Ubuntu) as backend servers, including web server installation (such as Apache or Nginx) via Bash or Azure CLI.
- Provide Linux/macOS steps for editing the hosts file (e.g., /etc/hosts), including commands for flushing DNS cache (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo dscacheutil -flushcache').
- Include Azure CLI or Bash alternatives for IIS/web server setup, avoiding exclusive reliance on PowerShell.
- Clarify that Application Gateway supports both Windows and Linux backend VMs, and offer parity in examples.
Application Gateway
Azure Application Gateway Backend Settings configuration
...les/application-gateway/configuration-http-settings.md
Medium Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation is generally platform-neutral and focuses on Azure Application Gateway configuration concepts. However, there are two notable instances of Windows bias: (1) troubleshooting guidance for Dedicated Backend Connections references Windows-specific authentication mechanisms (NTLM, Kerberos) and links to Windows and IIS documentation, and (2) Windows Authentication is mentioned before any Linux equivalents or generic authentication approaches. No PowerShell-heavy or missing Linux example bias is present, but Windows tools and patterns are referenced exclusively in troubleshooting sections.
Recommendations
- Add troubleshooting guidance for Linux-based backend authentication scenarios (e.g., SPNEGO, Kerberos on Linux, or generic OAuth/OpenID Connect).
- Include links to Linux documentation for Kerberos/SPN configuration and authentication, not just Windows/IIS.
- Clarify that backend authentication mechanisms may differ depending on the OS and provide parity for Linux/macOS users where possible.
- Where possible, mention generic approaches or cross-platform tools before Windows-specific ones.
Application Gateway
Azure Application Gateway listener configuration
...rticles/application-gateway/configuration-listeners.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
missing_linux_example
Summary
The documentation provides a code example for enabling HTTP/2 support using Azure PowerShell only, with no equivalent Azure CLI, Bash, or cross-platform example. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add equivalent Azure CLI example(s) for enabling HTTP/2 support, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Wherever possible, provide both PowerShell and CLI examples for configuration tasks.
- Explicitly mention that the Azure portal can be used for these configurations, and clarify if any features are only available via PowerShell.
- Review the documentation for any other sections where only Windows-centric tools or patterns are referenced, and add Linux-friendly alternatives.
Application Gateway
Configure an internal load balancer (ILB) endpoint
...configure-application-gateway-with-private-frontend-ip.md
Medium Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
powershell_heavy
windows_tools
Summary
The documentation demonstrates a notable Windows bias. All virtual machine examples use Windows Server images, and the only backend setup instructions involve installing IIS via PowerShell. The Cloud Shell is explicitly set to PowerShell, and the provided script is Windows-specific. There are no Linux VM examples, nor are there instructions for configuring a Linux-based backend (e.g., using NGINX or Apache). This makes it difficult for Linux users to follow the guide without significant adaptation.
Recommendations
- Provide parallel instructions for creating Linux virtual machines (e.g., Ubuntu) as backend servers.
- Include Linux-based backend configuration steps, such as installing NGINX or Apache using Bash/Cloud Shell.
- Show both PowerShell and Bash examples where scripts are required.
- Clarify that IIS/Windows is only one possible backend, and link to Linux-based backend pool configuration guides.
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_tools
windows_first
Summary
The documentation is generally platform-neutral, focusing on Azure networking concepts. However, there is a minor Windows bias in the 'Related content' section, where a link is provided to a guide on connecting virtual networks using PowerShell, a Windows-centric tool, without mentioning or linking to equivalent CLI or Bash guidance. Additionally, PowerShell is referenced before any cross-platform alternatives, which may create the impression that Windows tools are preferred or required.
Recommendations
- In the 'Related content' section, add links to equivalent Azure CLI and/or Bash-based guides for connecting virtual networks, if available.
- Where PowerShell is mentioned, clarify that Azure CLI and other cross-platform tools can also be used, and provide links or references to those alternatives.
- Ensure that examples and guidance throughout the documentation include both PowerShell and Azure CLI (or Bash) options when relevant.
API Center
Import APIs from Azure API Management - Azure API Center
...main/articles/api-center/import-api-management-apis.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides Azure CLI command examples for both Bash and PowerShell throughout, with Bash examples shown first and PowerShell examples following. There are no Windows-specific tools or patterns, and Linux parity is maintained in all examples. The only minor bias is that Bash (Linux/macOS) examples are shown before PowerShell (Windows), but both are equally represented.
Recommendations
- No changes needed for Linux parity; both Bash and PowerShell examples are provided.
- Consider clarifying that Azure CLI is fully cross-platform and can be used on Windows, Linux, and macOS.
- If desired, alternate the order of Bash and PowerShell examples or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
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 the PowerShell examples are formatted and presented immediately after the Bash examples in each step. There is a slight bias toward Windows/PowerShell users, as PowerShell examples are given equal prominence, and the PowerShell formatting is specifically called out. However, Linux users are not missing any information, and Bash examples are present throughout.
Recommendations
- Consider clearly labeling Bash and PowerShell examples with OS context (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)') to help users quickly identify relevant sections.
- If possible, present Bash (Linux/macOS) examples first, as Azure CLI is cross-platform and Bash is the default shell for many users.
- Add a brief note clarifying that both Bash and PowerShell examples are functionally equivalent and that Azure CLI works on all platforms.
- Ensure that any future additions do not default to Windows/PowerShell unless the feature is Windows-only.
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 shown immediately after Bash for each step, and the PowerShell formatting is explicitly called out. There is no evidence of missing Linux examples, but the presence of PowerShell examples and their prominence may create a slight Windows bias.
Recommendations
- Clearly label Bash and PowerShell examples with OS context (e.g., 'Linux/macOS (Bash)' and 'Windows (PowerShell)').
- Consider showing Bash (Linux/macOS) examples first, or providing a toggle to select preferred shell/OS.
- Ensure variable naming and command syntax are consistent and correct for each shell.
- Add a note clarifying that Bash examples are suitable for Linux/macOS users, and PowerShell for Windows users.
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation mentions Azure PowerShell alongside Azure CLI as tools for reviewing deployed resources, but does not provide explicit Linux/macOS examples or clarify cross-platform usage. Azure PowerShell is primarily associated with Windows, and its mention before Linux-native tools may subtly prioritize Windows users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Provide example commands for both Azure CLI and Azure PowerShell, with clear notes on platform compatibility.
- Mention that Azure PowerShell is available for Linux/macOS, if relevant, or recommend Azure CLI for Linux/macOS users.
- Consider listing Azure CLI before Azure PowerShell to reinforce cross-platform parity.
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, but PowerShell is mentioned prominently (in metadata and example tabs), and there is a slight preference for Windows/PowerShell tools. However, Azure CLI examples are also present, and no critical steps are Windows-only.
Recommendations
- Ensure that Azure CLI examples are always shown first, as CLI is cross-platform.
- Add explicit notes clarifying that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
- Consider including Bash shell scripting examples for Linux/macOS users, or at least mention that Azure CLI commands can be run in Bash.
- Review metadata (ms.custom: devx-track-azurepowershell) to ensure it doesn't imply PowerShell is required.
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 the Bicep file, but PowerShell is mentioned alongside CLI throughout, and PowerShell examples are given equal prominence. There is a slight bias in that PowerShell (a Windows-centric tool) is featured as a primary option, and the prerequisites section tracks Azure PowerShell requirements. However, Azure CLI (cross-platform) is also fully supported and shown first in the deployment section.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform.
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users about using Azure CLI and uploading files in Cloud Shell.
- Consider including a brief section on using Bicep directly (if supported) for advanced users on Linux/macOS.
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 provides instructions primarily through the Azure Portal and Azure CLI, with a single mention of Azure PowerShell as an alternative tool for disabling routing to a regional gateway. The PowerShell cmdlet is referenced after the Azure CLI and REST API, and no Windows-specific tools or patterns are prioritized. All code examples and instructions are platform-neutral or CLI-based, and there are no PowerShell-heavy sections or Windows-only tools. However, the PowerShell cmdlet is mentioned before explicitly referencing 'other Azure tools', which could be seen as a minor Windows-first ordering.
Recommendations
- Explicitly mention that all Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- When listing Azure tools, consider listing Azure CLI before PowerShell, or clarify parity between them.
- Add a note for Linux/macOS users about Azure CLI installation and usage if relevant.
- If referencing PowerShell, provide equivalent Bash or shell script examples when appropriate.
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 mentions Windows/PowerShell (Azure PowerShell) as an option for creating an AKS cluster before Linux alternatives (Azure CLI), but provides parity by also referencing the Azure CLI and Azure portal. All command examples use kubectl, which is cross-platform. No Windows-specific tools or patterns are used in the main deployment steps.
Recommendations
- List Azure CLI before Azure PowerShell in the prerequisites, as CLI is more widely used and cross-platform.
- Explicitly note that kubectl commands work on Windows, Linux, and macOS terminals.
- Consider providing links to Linux/macOS-specific installation guides for prerequisites (kubectl, Azure CLI).
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
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. The PowerShell example is given equal prominence to the CLI example, but there is no explicit mention of Linux/macOS alternatives for PowerShell. The CLI example is cross-platform, but the documentation does not clarify this or highlight Linux/macOS workflows. The prerequisites list both Azure CLI and Azure PowerShell without noting platform differences. There is minor bias in presenting PowerShell as a primary workflow without guidance for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note that Azure PowerShell is primarily for Windows, and suggest Bash or CLI for Linux/macOS.
- Consider showing Azure CLI examples first, or labeling them as recommended for non-Windows platforms.
- Explicitly state platform compatibility in the prerequisites section.
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_only_feature
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation is for gateway-required virtual network integration, which is explicitly stated to be a Windows-only feature. All examples and troubleshooting steps reference Windows tools (e.g., PowerShell's Test-NetConnection, netstat -aon), and there are no Linux/macOS equivalents or guidance. Linux users are excluded from using this feature, and the documentation does not provide parity or alternatives for Linux App Service plans.
Recommendations
- Clearly highlight at the top that this feature is Windows-only and unavailable for Linux apps.
- Where troubleshooting steps use Windows tools (PowerShell, netstat), add notes clarifying these are for Windows VMs and provide Linux/macOS equivalents (e.g., nc, ss, netstat, curl) for general network troubleshooting.
- Link to documentation for regional virtual network integration, which supports Linux apps, and provide migration guidance for Linux users.
- Add a comparison table summarizing feature availability for Windows vs. Linux App Service plans.
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.