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 2001-2025 of 2121 flagged pages
App Service Manage App Service Certificates ...s/app-service/configure-ssl-app-service-certificate.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides command-line examples for exporting App Service certificates using Azure CLI and Azure PowerShell, with PowerShell examples included and referenced in the FAQ. While the Azure CLI is cross-platform, PowerShell is primarily associated with Windows. The order of presentation places the Azure portal first, then CLI, then PowerShell, which is a reasonable sequence, but the inclusion of PowerShell-specific instructions and FAQ entries may suggest a slight Windows bias. No Linux/macOS-specific tools or troubleshooting are mentioned, and there are no explicit Linux/macOS examples or notes.
Recommendations
  • Add explicit notes confirming that all CLI commands work on Linux/macOS, and provide troubleshooting tips for those platforms if relevant.
  • Include Linux/macOS-specific instructions or examples where file handling, permissions, or certificate import/export processes may differ.
  • Reference cross-platform alternatives to PowerShell, such as bash scripts, especially for certificate handling.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
GitHub Create Pull Request
App Service Prerequisites ...cludes/tutorial-microsoft-graph-as-app/introduction.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions to a managed identity. However, the PowerShell example is presented first and is more detailed, which may suggest a Windows-first approach. The PowerShell script uses modules and patterns familiar to Windows users, while the Azure CLI example is provided but with less explanation. No Linux/macOS-specific tools or shell examples are given, and there is no mention of platform-specific considerations for running these commands.
Recommendations
  • Alternate the order of examples, sometimes showing Azure CLI first to balance platform representation.
  • Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and provide guidance for Linux/macOS users if any steps differ.
  • Add bash shell examples for common tasks, or clarify that Azure CLI commands can be run in bash/zsh on Linux/macOS.
  • Note any prerequisites or installation steps for Azure CLI on Linux/macOS.
  • Consider adding troubleshooting notes for non-Windows environments if relevant.
GitHub Create Pull Request
App Service https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-nodejs-mongodb-app/deploy-zip-curl-commands.md ...utorial-nodejs-mongodb-app/deploy-zip-curl-commands.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for deploying via curl, but the PowerShell example includes an additional explanatory note specific to Windows/PowerShell users. The Bash example is presented first, but the PowerShell example receives more detailed attention, suggesting a slight Windows bias.
Recommendations
  • Add equivalent explanatory notes for Bash users if there are any shell-specific caveats.
  • Ensure parity in detail and troubleshooting tips for both Bash and PowerShell sections.
  • Consider including macOS-specific notes if there are differences in curl usage or authentication.
  • Explicitly state that both examples work on Linux, macOS, and Windows, and clarify any platform-specific differences.
GitHub Create Pull Request
App Service Set Up Azure Arc for App Service, Functions, and Logic Apps .../articles/app-service/manage-create-arc-environment.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell examples are always shown immediately after Bash, and in some cases, the variable naming and structure are more tailored to PowerShell conventions. There is a slight 'Windows-first' bias in the ordering and presence of PowerShell examples, but Linux users are not blocked from completing any steps. All commands are cross-platform Azure CLI and kubectl, with no Windows-only tools or patterns.
Recommendations
  • Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
  • Consider showing Bash examples first, or grouping Bash and PowerShell examples side-by-side to avoid perceived prioritization.
  • Add a note clarifying that Azure CLI and kubectl commands work on Linux/macOS and Windows equally.
  • Where variable naming conventions differ, provide a brief explanation for Linux/macOS users.
  • Ensure that any platform-specific caveats (e.g., file paths, environment variable syntax) are called out.
GitHub Create Pull Request
App Service Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes ...b/main/articles/app-service/migrate-app-service-arc.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell examples are always shown immediately after CLI, and no Linux/macOS-specific shell examples (e.g., Bash, shell scripting) are given. The use of PowerShell may be more familiar to Windows users, and its inclusion in every example could suggest a slight Windows bias. However, the CLI examples are cross-platform and shown first, and there is explicit mention that only Linux containers are supported (no Windows support), which is relevant for parity.
Recommendations
  • Consider explicitly stating that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
  • Add Bash or shell script equivalents for common tasks, or clarify that the Azure CLI commands can be run in Bash on Linux/macOS.
  • If PowerShell is not required for Linux/macOS users, consider moving PowerShell examples to a separate section or appendix.
  • Add a note about installing Azure CLI on Linux/macOS, if relevant.
GitHub Create Pull Request
App Service Supported platforms and file types ...includes/webjobs-create/webjobs-supported-platforms.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation lists Windows hosting options before Linux, and Windows-specific file types (.exe, .cmd, .bat) and PowerShell scripts (.ps1) are mentioned before Linux equivalents. Windows tools and patterns are emphasized, while Linux tools (e.g., Bash scripts) are listed later and without examples.
Recommendations
  • List Linux and Windows hosting options in a neutral or alternating order to avoid perceived priority.
  • Present Linux file/script types (e.g., .sh) alongside or before Windows types.
  • Include explicit examples for both Windows and Linux script execution.
  • Highlight Linux tools and patterns (e.g., Bash, shell scripting) with equal prominence to Windows tools.
GitHub Create Pull Request
App Service Back Up an App ...e-docs/blob/main/articles/app-service/manage-backup.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias. Windows terminology and paths (e.g., %HOME%, D:\home\site\wwwroot) are used as defaults, and Windows-specific tools like Kudu DebugConsole and FTP are referenced without mentioning Linux alternatives. Examples and instructions for file operations (e.g., creating _backup.filter) use Windows paths and tools first, with Linux equivalents only briefly referenced or omitted. Automation mentions Azure PowerShell alongside Azure CLI, but CLI examples are cross-platform. The documentation does not provide explicit Linux/macOS file management examples or clarify platform differences for accessing app files.
Recommendations
  • Provide Linux/macOS equivalents for file paths (e.g., /home/site/wwwroot) alongside Windows paths in all examples.
  • Include instructions for creating and uploading _backup.filter using Linux/macOS tools (e.g., SCP, SFTP, Linux shell commands) and clarify how to access Kudu/FTP from non-Windows systems.
  • Mention that Azure CLI commands are cross-platform and highlight any OS-specific considerations.
  • Avoid using Windows paths and terminology as the default; present both Windows and Linux examples side by side.
  • Clarify any differences in app file system structure or access methods between Windows and Linux App Service plans.
GitHub Create Pull Request
App Service Authentication and Authorization ...s/app-service/overview-authentication-authorization.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides a balanced overview of authentication and authorization in Azure App Service, with clear distinctions between Windows and Linux/container architectures. However, the 'Feature architecture' section describes the Windows (IIS module) implementation before the Linux/container approach, and references to IIS modules are Windows-specific. There are no explicit PowerShell-heavy examples or missing Linux examples, but the ordering and tool references show minor Windows bias.
Recommendations
  • Present Linux/container architecture before or alongside Windows to avoid implicit prioritization.
  • Clarify that IIS modules are Windows-specific and provide equivalent technical context for Linux/container users.
  • Where Windows tools (e.g., IIS) are mentioned, explicitly state the Linux/container equivalent or note differences.
  • Ensure that any future code/configuration examples use cross-platform tools (e.g., az CLI, REST API) and avoid Windows-only tooling.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools and examples (Azure PowerShell, Azure portal) before Linux-friendly equivalents (Azure CLI, ARM templates, Terraform). The 'Related content' section puts PowerShell and portal quickstarts ahead of CLI and template options, which may create friction for Linux/macOS users. No explicit Linux examples or guidance are provided, but the content is not strictly Windows-only.
Recommendations
  • Reorder 'Related content' to list Azure CLI and ARM template quickstarts before PowerShell and portal options.
  • Add explicit notes or examples for Linux/macOS users, especially for command-line tasks.
  • Ensure that all referenced scripts and quickstarts have Linux/macOS parity and are clearly marked as cross-platform.
  • Where PowerShell is mentioned, also mention Bash/CLI alternatives.
  • Include a brief section clarifying that all features and steps apply equally to Linux-hosted apps and Linux-based client environments.
GitHub Create Pull Request
App Service Integrate your app with an Azure virtual network ...main/articles/app-service/overview-vnet-integration.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific features and limitations (e.g., Windows Containers subnet sizing) are described in detail, while Linux-specific details are limited to a brief mention of network dependencies for Linux continuous deployment. Most examples, calculations, and operational guidance focus on Windows scenarios, with Linux equivalents either missing or relegated to a short section. No Linux/Powershell/CLI example parity is provided, and Windows terminology (e.g., Windows Server Active Directory, NetBIOS) is referenced without Linux alternatives.
Recommendations
  • Add Linux-specific examples and operational guidance, such as subnet sizing for Linux containers and common Linux deployment scenarios.
  • Provide parallel CLI and scripting examples for both Windows (PowerShell) and Linux (Bash), especially in troubleshooting and configuration sections.
  • Include Linux/macOS terminology and patterns (e.g., reference Linux authentication mechanisms, file system mounts, etc.) where Windows-specific features are mentioned.
  • Ensure that Linux-related limitations and best practices are described with the same level of detail as Windows.
  • Present examples and guidance for both platforms side-by-side, or clearly indicate platform-specific differences.
GitHub Create Pull Request
App Service Create an App by Using a Terraform Template ...n/articles/app-service/provision-resource-terraform.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates some Windows bias, particularly in the 'Prerequisites' section, where Windows and PowerShell configuration options are listed before Linux equivalents. There is a notable emphasis on Windows tools (PowerShell, Visual Studio Code) and Windows-specific instructions, though Linux options are present. The main Terraform implementation and validation steps use generic Bash commands, which are cross-platform, and both Linux and Windows container templates are provided. However, Windows is often mentioned first and more prominently, which may create minor friction for Linux/macOS users.
Recommendations
  • List Linux/Bash configuration options before Windows/PowerShell options in the prerequisites.
  • Explicitly mention macOS support and provide links or instructions for macOS users.
  • Ensure parity in examples and instructions for both Linux and Windows, including tool installation and usage.
  • Where Visual Studio Code is referenced, clarify that it is available on Linux and macOS, not just Windows.
  • Avoid using Windows-specific terminology (e.g., PowerShell) as the default; present Bash or cross-platform options first.
GitHub Create Pull Request
App Service Create a scheduled WebJob with prebuilt samples ...s/blob/main/articles/app-service/quickstart-webjobs.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page displays a mild Windows bias: Windows examples and tools (CMD, Batch, PowerShell, F#) are listed first and in greater variety than Linux equivalents. The Windows tab includes more scripting options (CMD, Batch, PowerShell, F#) not present in the Linux tab, which only offers Bash and language-specific samples. Windows-specific tools and patterns (CMD, Batch, PowerShell) are mentioned exclusively in the Windows section, with no Linux shell scripting equivalents (e.g., no mention of shell scripts beyond Bash). However, Linux users can still complete the task using provided samples for major languages.
Recommendations
  • Add Linux shell scripting examples beyond Bash, such as zsh or sh, if relevant.
  • Include parity for scripting languages (e.g., provide F# or other language samples for Linux if supported).
  • Present both Windows and Linux tabs in parallel, or default to a neutral order (alphabetical or by popularity) to avoid Windows-first perception.
  • Explicitly mention any limitations or differences in scripting support between platforms.
  • Consider adding a table summarizing feature parity between Windows and Linux WebJobs.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses Microsoft Graph as the app| Azure ...e/scenario-secure-app-access-microsoft-graph-as-app.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides installation instructions for the required NuGet packages using both the .NET Core CLI and the Visual Studio Package Manager Console. However, the Visual Studio/PowerShell example is given equal prominence to the cross-platform CLI, and the Package Manager Console is a Windows-only tool. There are no Linux/macOS-specific instructions or mentions of platform differences. The order of presentation slightly favors Windows by listing the Package Manager Console after the CLI, but does not provide parity for Linux users (e.g., instructions for using VS Code or other editors).
Recommendations
  • Explicitly state that the .NET Core CLI commands work on Linux/macOS as well as Windows.
  • Add instructions for installing NuGet packages using VS Code or JetBrains Rider, which are popular on Linux/macOS.
  • Clarify that the Package Manager Console is only available in Visual Studio on Windows.
  • Consider listing the cross-platform CLI instructions first to emphasize platform neutrality.
  • Mention any platform-specific prerequisites or differences if relevant.
GitHub Create Pull Request
App Service Tutorial - .NET Web app accesses Microsoft Graph as the user | Azure ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-user.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both .NET CLI and Visual Studio Package Manager Console instructions for installing NuGet packages, but lists the Visual Studio/PowerShell method second. However, the Package Manager Console example uses PowerShell syntax, which is Windows-specific. There are no explicit Linux/macOS instructions for using alternative IDEs or editors (e.g., VS Code, JetBrains Rider), nor is there mention of Linux-specific package management or environment setup. The overall flow assumes Visual Studio and Windows-centric tooling, though the .NET CLI commands are cross-platform.
Recommendations
  • Explicitly state that the .NET CLI commands work on Linux/macOS and are recommended for cross-platform development.
  • Add instructions for installing packages using VS Code, JetBrains Rider, or other cross-platform editors.
  • Clarify that the Package Manager Console is a Visual Studio (Windows) feature and suggest alternatives for non-Windows users.
  • Consider listing the .NET CLI method first to emphasize cross-platform compatibility.
  • Add a note or section about environment setup on Linux/macOS (e.g., installing .NET SDK, configuring appsettings.json paths).
GitHub Create Pull Request
App Service Build a scheduled WebJob using your preferred language ...ocs/blob/main/articles/app-service/tutorial-webjobs.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The .NET section of the documentation gives explicit, detailed instructions for both Windows and Linux, but Windows examples (such as dotnet publish and zip commands) are presented first, and the structure is more elaborate for Windows (e.g., explicit mention of .exe, Windows runtime). The reference to supported file types and CRON expressions links to pages with 'windowscode' tabs, suggesting a Windows-centric approach. Other language pivots (Python, Node, Java, PHP) are Linux-focused, but the overall documentation and screenshots are not platform-neutral, and Windows terminology/tools are often foregrounded.
Recommendations
  • Present Linux and Windows instructions side-by-side or in parallel tabs, not with Windows first.
  • Ensure all references (such as supported file types and CRON expressions) link to platform-neutral or Linux-specific documentation where appropriate.
  • Add more explicit Linux/macOS instructions for .NET, including common troubleshooting tips for Linux users.
  • Use neutral terminology and avoid assuming Windows as the default platform.
  • Include screenshots and examples for Linux environments where possible.
GitHub Create Pull Request
App Service Use Key Vault References as App Settings ...ticles/app-service/app-service-key-vault-references.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key configuration steps, but consistently lists PowerShell examples immediately after CLI, with no mention of Linux/macOS-specific shell or scripting patterns. There are no bash or Linux-native command examples, and PowerShell is a Windows-centric tool. However, the CLI examples are cross-platform, and no steps are strictly Windows-only.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
  • Add bash script examples or notes for Linux/macOS users where PowerShell is shown.
  • Clarify that PowerShell examples are for Windows users, and suggest alternatives for Linux/macOS users.
  • Consider listing CLI examples before PowerShell, or grouping them together as cross-platform and Windows-specific.
GitHub Create Pull Request
App Service Quickstart: Use Terraform to configure an Azure App Service Environment v3 ...articles/app-service/environment/creation-terraform.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell tab is present and detailed, which may indicate a slight Windows bias. The Azure CLI instructions are cross-platform, but PowerShell is a Windows-centric tool (though available on Linux/macOS). The order of tabs (CLI first, then PowerShell) is appropriate, but PowerShell examples may create friction for Linux/macOS users who are less likely to use it.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Note that Azure PowerShell is available on Linux/macOS, but CLI is more commonly used outside Windows.
  • Consider adding Bash script examples for common tasks (e.g., resource cleanup) to further support Linux users.
  • Explicitly mention platform compatibility for each tool in the prerequisites section.
GitHub Create Pull Request
App Service Migration Checklist - Azure App Service on Arc-enabled Kubernetes to Azure Container Apps on Arc-enabled Kubernetes ...b/main/articles/app-service/migrate-app-service-arc.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for resource queries, but PowerShell is always listed immediately after CLI and before any mention of Linux shell equivalents. There are no bash or Linux shell examples, and PowerShell is a Windows-centric tool. The documentation does not mention Linux-specific tools or patterns for these tasks, nor does it clarify that Azure CLI is cross-platform. However, the core migration steps and requirements are Linux-focused, as Azure Container Apps on Arc-enabled Kubernetes only supports Linux containers.
Recommendations
  • Add bash or Linux shell examples for running Azure CLI commands, demonstrating usage on Linux/macOS.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
  • Consider listing CLI examples before PowerShell, or grouping them together with explicit OS context.
  • Note that PowerShell Core is available cross-platform, but most Linux users will use bash/zsh.
  • Explicitly state that no Windows container support is available for Azure Container Apps on Arc-enabled Kubernetes.
GitHub Create Pull Request
App Service Create an App by Using a Terraform Template ...n/articles/app-service/provision-resource-terraform.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias in several areas: Windows and PowerShell configuration options are listed alongside Linux/Bash, but Windows-specific options (including PowerShell) are mentioned before Linux equivalents in the prerequisites. There is also a focus on Windows tooling (Visual Studio Code extension) without mentioning Linux-specific editor alternatives. However, the main Terraform examples are provided for both Linux and Windows containers, and implementation steps use Bash commands, which are cross-platform.
Recommendations
  • List Linux/Bash options before Windows/PowerShell options in the prerequisites to avoid implicit prioritization.
  • Include explicit instructions or links for configuring Terraform on Linux/macOS outside of Azure Cloud Shell.
  • Mention alternative editors for Linux users (e.g., Vim, Emacs, JetBrains IDEs) or clarify that VS Code is cross-platform.
  • Ensure that all command-line examples are explicitly marked as cross-platform or provide platform-specific notes where necessary.
  • Add a note clarifying that PowerShell is available on Linux/macOS, or provide Bash equivalents for any PowerShell-specific instructions.
GitHub Create Pull Request
App Service Use Private Endpoints for Apps ...main/articles/app-service/overview-private-endpoint.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Windows-centric tools and examples before Linux equivalents, notably in the 'Related content' section, where Azure PowerShell is mentioned before ARM templates and Terraform. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained through CLI and Terraform references. No explicit Linux examples or tools are missing, but Windows/PowerShell is presented first.
Recommendations
  • Reorder related content to list cross-platform tools (Azure CLI, ARM templates, Terraform) before Windows-specific tools (PowerShell).
  • Explicitly mention that Azure CLI and Terraform are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is referenced, add a note or link to equivalent Azure CLI instructions for Linux/macOS users.
  • Include a brief section or callout confirming that all features and steps apply equally to Linux-hosted apps and Linux-based client environments.
GitHub Create Pull Request
App Service Configure Premium V3 Tier ...s/app-service/app-service-configure-premium-v3-tier.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating Premium V3 tier configuration, but the PowerShell example is given equal prominence despite being Windows-centric. In sections discussing SKU availability, Windows SKU availability is listed before Linux, and the Linux command is presented as a variant rather than a primary example. Portal screenshots and instructions are platform-neutral, but scripting and automation lean toward Windows tools and patterns.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid implicit prioritization.
  • Add explicit Bash shell script examples for Linux/macOS users where PowerShell is shown.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where PowerShell is mentioned, note its Windows focus and suggest alternatives for Linux/macOS.
  • Ensure any references to 'Development tools' or cloning apps mention cross-platform compatibility.
GitHub Create Pull Request
App Service Configure Premium v4 Tier ...s/app-service/app-service-configure-premium-v4-tier.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias by listing Windows SKU availability before Linux, providing both Azure CLI and PowerShell automation examples (with PowerShell being Windows-centric), and referencing Windows-specific hosting details. However, Linux equivalents are present, and Azure CLI examples are cross-platform.
Recommendations
  • Present Linux and Windows examples side-by-side or in parallel sections, rather than listing Windows first.
  • Add explicit Bash scripting examples for Linux/macOS users in the automation section.
  • Clarify that Azure CLI commands work on all platforms and highlight this fact.
  • Include notes or links for Linux/macOS users regarding PowerShell Core compatibility if PowerShell is referenced.
  • Ensure any references to Windows tools or patterns are matched with Linux/macOS equivalents.
GitHub Create Pull Request
App Service Disable Basic Authentication for Deployment ...n/articles/app-service/configure-basic-auth-disable.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page shows a mild Windows bias. Windows-centric deployment tools like Web Deploy and Visual Studio are referenced throughout, and troubleshooting sections specifically mention Windows agents and the 'windows-latest' pipeline agent. While Azure CLI examples are provided (which are cross-platform), there are no explicit Linux/macOS-specific examples or troubleshooting guidance. Windows tools and patterns (Web Deploy, Visual Studio) are mentioned before their Linux equivalents, and some troubleshooting guidance is focused on Windows agents.
Recommendations
  • Add explicit Linux/macOS troubleshooting steps for deployment scenarios, especially where Windows agents are discussed.
  • Include examples of using Linux-native deployment tools (e.g., SCP, rsync, SFTP) where relevant, or clarify their applicability.
  • When discussing Azure Pipelines, provide parity in guidance for self-hosted Linux/macOS agents.
  • Where Visual Studio or Web Deploy are mentioned, also reference cross-platform alternatives (e.g., VS Code, Azure CLI, Git).
  • Ensure that example commands and screenshots are not Windows-centric, and add Linux/macOS equivalents if needed.
GitHub Create Pull Request
App Service Configure ASP.NET Core apps .../articles/app-service/configure-language-dotnetcore.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page shows a mild Windows bias: Windows instructions and tooling (Visual Studio, Kudu, PowerShell/CMD) are presented first or exclusively in some sections, and Windows-centric patterns (such as using Visual Studio for publishing and Kudu for runtime inspection) are described in more detail. Linux instructions are present and generally complete, but Windows tools and workflows are often mentioned before their Linux equivalents, and some sections (like multi-project deployment) assume Visual Studio as the default, which is more common on Windows.
Recommendations
  • Ensure Linux instructions are presented with equal prominence and detail as Windows instructions, especially in introductory and critical sections.
  • Provide Linux-first examples in some sections to balance the order of presentation.
  • Expand on Linux-native workflows (e.g., VS Code, CLI, container-based deployment) where Visual Studio/Kudu are emphasized.
  • Where Windows tools are mentioned (Kudu, PowerShell), provide equivalent Linux tooling or clarify alternatives (e.g., SSH, Bash, Azure CLI).
  • Add explicit cross-platform notes for steps that differ between Windows and Linux, especially for build, deployment, and diagnostics.
GitHub Create Pull Request
App Service Manage App Service Certificates ...s/app-service/configure-ssl-app-service-certificate.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for exporting certificates, but PowerShell is given its own dedicated section and is mentioned in the FAQ. There is no explicit Linux/macOS bias, but the ordering and inclusion of PowerShell-specific instructions and troubleshooting suggest a mild Windows-first approach. All command-line examples are cross-platform (Azure CLI and PowerShell), but PowerShell is Windows-centric and shown after CLI. No Linux-specific tools or troubleshooting are mentioned.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide example shell commands (e.g., bash) for common certificate management tasks.
  • Add troubleshooting notes for Linux/macOS users, such as file permissions or differences in handling .pfx files.
  • Reorder command-line sections to show Azure CLI (cross-platform) before PowerShell, and clarify platform compatibility.
  • Include a note that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
GitHub Create Pull Request
← Previous Page 81 of 85 Next →