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 1751-1775 of 2121 flagged pages
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes a development environment that is compatible with .NET and Azure App Service, and it references GitHub Codespaces and Azure Developer CLI (azd) for deployment. While these tools are cross-platform, the tutorial is heavily oriented toward ASP.NET Core and does not provide any Linux-specific or non-Windows terminal instructions. There are no examples or notes for Linux users, such as using bash, zsh, or Linux-specific deployment patterns. All code and deployment steps are presented in a way that is most familiar to Windows/.NET developers, and there is no mention of alternative Linux-first workflows or tools.
Recommendations
- Explicitly mention that all terminal commands (dotnet, azd) work on Linux, macOS, and Windows, and provide any necessary prerequisites for Linux users (e.g., installing .NET SDK, azd CLI on Linux).
- Include a note or section for Linux users, such as how to run the sample app in a local Linux environment (e.g., using bash, systemd, or Docker).
- Provide example commands using bash/zsh syntax where appropriate, especially for steps like exporting environment variables or running the app.
- Clarify that Azure App Service supports both Windows and Linux hosting, and provide guidance for deploying to both platforms if there are differences.
- If any step is different on Linux (such as file paths, case sensitivity, or permissions), call this out explicitly.
Create Pull Request
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section, the only example given for clearing DNS cache is the Windows-specific 'ipconfig /flushdns' command, with no mention of Linux or macOS equivalents. This presents a subtle Windows-first bias and omits guidance for users on other operating systems.
Recommendations
- When providing command-line troubleshooting steps (such as clearing DNS cache), include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Explicitly mention that the instructions apply to all platforms, or provide platform-specific notes where relevant.
- Review other troubleshooting or command-line examples to ensure parity across Windows, Linux, and macOS.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides instructions only for deleting resources via the Azure portal, which is a graphical interface commonly associated with Windows users. There are no examples or instructions for performing the same task using command-line tools such as Azure CLI or Bash, which are preferred by many Linux users. This omission may make the documentation less accessible or convenient for Linux users or those who prefer automation.
Recommendations
- Add Azure CLI examples for deleting the resource group, including both Windows (PowerShell) and Linux (Bash) command syntax.
- Explicitly mention that the Azure portal is cross-platform, but also provide command-line alternatives for users who prefer not to use the GUI.
- Ensure that future documentation includes both GUI and CLI instructions, with equal prominence given to Linux-friendly tools.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a troubleshooting step for clearing the DNS cache that only references the Windows command ('ipconfig /flushdns'), without mentioning the equivalent command for Linux or macOS. No Linux or cross-platform alternatives are provided, which may leave non-Windows users without clear guidance.
Recommendations
- Include equivalent DNS cache flush commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo service nscd restart') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder') alongside the Windows example.
- Wherever platform-specific instructions are given, provide parity for major operating systems (Windows, Linux, macOS) or link to external resources with platform-specific guidance.
- Review the documentation for other implicit Windows-centric assumptions and ensure cross-platform inclusivity in troubleshooting and automation sections.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes a development environment based on .NET and Azure App Service, which are cross-platform, but all examples and instructions are tailored to a workflow that is most familiar to Windows users (e.g., Visual Studio Codespaces, .NET CLI, Azure CLI). There are no explicit Linux or macOS terminal instructions, nor are there any references to Linux-specific tools or deployment patterns. The documentation does not mention or show how to perform these steps on a native Linux environment, nor does it provide parity for Linux users in terms of setup, testing, or deployment.
Recommendations
- Explicitly mention that all steps work on Linux, macOS, and Windows, and provide any necessary prerequisites for Linux users (e.g., installing .NET SDK, Azure CLI).
- Add Linux/macOS-specific terminal commands or notes where file paths, environment variables, or tooling may differ (e.g., export vs set for environment variables).
- Include screenshots or terminal output from a Linux shell (e.g., bash) to demonstrate parity.
- If using Codespaces, clarify that it is a Linux-based environment and highlight any differences from local Windows development.
- Mention alternative editors or IDEs commonly used on Linux (e.g., VS Code, JetBrains Rider) if relevant.
- Ensure that all deployment and testing steps are validated on Linux and document any platform-specific caveats.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/scenario-secure-app-access-microsoft-graph-as-app.md
...e/scenario-secure-app-access-microsoft-graph-as-app.md
Medium Priority
View Details →
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 Package Manager Console example is PowerShell-based and references Visual Studio, a Windows-centric tool, and it is presented after the cross-platform .NET CLI example. There are no explicit Linux-only instructions, but the focus on Visual Studio and PowerShell may implicitly favor Windows users.
Recommendations
- Explicitly mention that the .NET Core CLI commands work on Linux, macOS, and Windows, and recommend them as the primary, cross-platform approach.
- Clarify that the Package Manager Console is only available in Visual Studio (Windows), and provide alternative instructions for Linux users (e.g., using Visual Studio Code or JetBrains Rider).
- Consider removing or de-emphasizing Windows-specific tooling unless there is a Linux equivalent, or at least provide parity in instructions for Linux development environments.
- Add a note or section on how to run and debug the sample code on Linux, including any prerequisites or differences.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and avoids explicit Windows-only tooling or PowerShell-heavy instructions. However, in the troubleshooting section about clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is provided, with no mention of Linux or macOS equivalents. This presents a subtle 'windows_first' and 'missing_linux_example' bias, as users on other platforms are not given guidance.
Recommendations
- When mentioning platform-specific commands (such as clearing DNS cache), provide equivalent instructions for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Explicitly state that the instructions apply to all platforms, and where differences exist, provide parallel steps for Windows, Linux, and macOS.
- Review other troubleshooting or command-line guidance to ensure parity for non-Windows users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-ip-restrictions.md
...in/articles/app-service/app-service-ip-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for managing access restrictions, but PowerShell examples are consistently present and sometimes shown first or exclusively in advanced scenarios. There are no explicit Linux shell (bash) or platform-agnostic scripting examples outside of Azure CLI. The documentation assumes familiarity with PowerShell cmdlets, which are more common in Windows environments, and does not highlight Linux-native tooling or workflows beyond Azure CLI.
Recommendations
- Ensure that for every PowerShell example, an equivalent Azure CLI (bash-friendly) example is provided and shown with equal prominence.
- Where possible, provide bash script snippets or explicit Linux shell usage, especially for advanced scenarios (e.g., multi-source rules, HTTP header filtering), not just PowerShell.
- In tabbed code sections, alternate the order so that Azure CLI is not always after PowerShell, or default to Azure CLI as the first tab to avoid Windows-first perception.
- Explicitly mention that Azure CLI commands work cross-platform (Windows, macOS, Linux), and encourage their use for Linux users.
- If certain features are only available via PowerShell, clearly state this and provide workarounds or alternatives for Linux users where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation only provides instructions for cleaning up resources via the Azure portal, which is a GUI-based method commonly associated with Windows users. There are no examples or instructions for performing the same task using command-line tools such as Azure CLI or Bash, which are preferred by many Linux users. This omission may make it less accessible for Linux users or those who prefer command-line interfaces.
Recommendations
- Add equivalent instructions for deleting the resource group using Azure CLI (az group delete) with example commands.
- Provide both Windows (PowerShell) and Linux (Bash) command-line examples where relevant.
- Explicitly mention that the Azure portal method is cross-platform, but highlight command-line alternatives for users on Linux or those who prefer automation.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Azure portal steps and DNS configuration. However, in the troubleshooting section, the only example for clearing the DNS cache is for Windows (`ipconfig /flushdns`), with no equivalent command or mention for Linux or macOS users. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps such as clearing the DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Explicitly mention that the instructions apply to all platforms, and provide platform-specific notes where appropriate.
- Review other troubleshooting and automation sections to ensure parity of examples and commands for Linux, macOS, and Windows users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for granting Microsoft Graph permissions, but the PowerShell example is presented first and in greater detail, which may indicate a slight Windows-first and PowerShell-heavy bias. There are no explicit Linux shell or bash examples, and the PowerShell script is more prominent, which could disadvantage Linux users who are less familiar with PowerShell.
Recommendations
- Present Azure CLI (bash/shell) examples before PowerShell, or at least give them equal prominence.
- Explicitly mention that Azure CLI commands work cross-platform (Linux, macOS, Windows) to encourage non-Windows users.
- Consider providing bash script examples where appropriate, especially for steps that involve scripting.
- Add a note clarifying that PowerShell Core is cross-platform, but that Azure CLI is generally preferred for Linux environments.
- Ensure that screenshots and UI instructions are not specific to Windows environments.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/manage-scale-up.md
...docs/blob/main/articles/app-service/manage-scale-up.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing App Service pricing details specifically for Windows (e.g., linking to 'app-service/windows/' in pricing), and does not provide any Linux-specific guidance or examples. There are no command-line or scripting examples (PowerShell, CLI, Bash), but the absence of Linux-specific information and the use of Windows-centric links indicate a lack of parity.
Recommendations
- Include links and references to both Windows and Linux App Service pricing details where appropriate.
- Add explicit notes or sections clarifying any differences in scaling behavior or features between Windows and Linux App Service plans.
- Provide examples or screenshots for both Windows and Linux App Service plans if the portal experience or options differ.
- Ensure related documentation (e.g., scaling databases) also covers both Windows and Linux hosting scenarios where relevant.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally platform-neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section for clearing DNS cache, only the Windows-specific command (`ipconfig /flushdns`) is provided, with no mention of Linux or macOS equivalents. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps that involve OS-level commands, include equivalent instructions for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo service nscd restart`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Explicitly state that the instructions apply to all platforms, or provide platform-specific tabs or notes where relevant.
- Review other troubleshooting or command-line sections to ensure parity for non-Windows users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation assumes a development environment that is compatible with .NET and Azure App Service, but it does not provide explicit Linux or cross-platform instructions. All terminal commands and deployment steps are generic (e.g., 'dotnet run', 'azd up'), which work on both Windows and Linux, but there are no Linux-specific examples or mentions of Linux tools. The workflow references GitHub Codespaces (which is Linux-based), but does not clarify this or provide parity guidance for local Linux development. There is no mention of PowerShell or Windows-only tools, but the lack of explicit Linux instructions or troubleshooting tips may create an implicit bias toward Windows users.
Recommendations
- Explicitly state that all commands work on both Windows and Linux, and clarify any OS-specific prerequisites.
- Add a section or notes for users developing on local Linux or macOS environments, including any differences in setup or troubleshooting.
- Provide example shell commands using bash/zsh where appropriate, especially for common Linux workflows (e.g., using curl to test endpoints).
- Mention that GitHub Codespaces runs on Linux, and provide guidance for replicating the environment locally on Linux.
- If referencing deployment or development tools, ensure both Windows and Linux equivalents are mentioned (e.g., Azure CLI usage in bash vs PowerShell).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally platform-neutral, focusing on Azure portal steps and DNS configuration. However, in the troubleshooting section, the only example given for clearing the DNS cache is for Windows (`ipconfig /flushdns`), with no mention of the equivalent commands for Linux or macOS. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing command-line instructions (such as clearing DNS cache), include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- If referencing OS-specific troubleshooting steps, present them in a cross-platform way, either listing all major OSes together or linking to a cross-platform troubleshooting guide.
- Review other sections for similar subtle platform-specific references and ensure parity for Linux and macOS users.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-set-up-app-service-authentication/intro.md
...es/tutorial-set-up-app-service-authentication/intro.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses on enabling authentication for Azure App Service but only references configuration via the Azure portal and app settings, without providing any command-line examples. There is no mention of Linux-specific tools or workflows (such as Azure CLI on Linux), nor are there any examples using Bash or Linux shell environments. The lack of cross-platform command-line instructions implicitly prioritizes the Windows GUI experience, which is more common for Windows users.
Recommendations
- Add step-by-step examples using Azure CLI commands that can be run on Linux, macOS, or Windows.
- Include Bash shell snippets alongside any PowerShell or portal instructions.
- Explicitly mention that configuration can be performed from any platform, and provide parity in instructions for both Windows and Linux users.
- If referencing app settings, show how to set them using both Azure Portal (GUI) and Azure CLI (cross-platform).
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation only provides instructions for cleaning up resources via the Azure portal, which is a graphical interface commonly associated with Windows workflows. There are no examples or instructions for performing the same task using cross-platform tools such as the Azure CLI or Bash scripts, which are preferred by many Linux users.
Recommendations
- Add equivalent instructions for deleting the resource group using the Azure CLI, with example commands.
- Include both Windows (PowerShell) and Linux (Bash) command-line examples where applicable.
- Explicitly mention that the Azure portal is cross-platform, but also provide command-line alternatives for users who prefer non-GUI workflows.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI scripts for granting Microsoft Graph API permissions, but PowerShell is presented first and in greater detail. PowerShell is more commonly associated with Windows environments, and its placement before the cross-platform Azure CLI may signal a preference for Windows tooling. There are no explicit Linux-specific instructions or examples, and the PowerShell example is more verbose and detailed than the Azure CLI example.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
- Ensure parity in detail and explanation between PowerShell and Azure CLI examples.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any Linux-specific notes if relevant.
- Consider including Bash script examples or notes for Linux users where appropriate.
- Avoid assuming Visual Studio usage, as it is primarily a Windows tool; mention cross-platform alternatives (e.g., VS Code, command-line deployment) where possible.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform neutral, focusing on Azure Portal UI steps. However, in the troubleshooting section, only a Windows-specific method ('ipconfig /flushdns') is provided for clearing the DNS cache, with no mention of Linux or macOS equivalents. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing command-line troubleshooting steps (such as clearing DNS cache), include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- If referencing OS-specific tools or commands, present them for all major platforms or link to external documentation covering all platforms.
- Consider adding a short note or table summarizing how to clear DNS cache on Windows, Linux, and macOS to ensure parity.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
...service/tutorial-ai-integrate-azure-ai-agent-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation assumes a development environment based on .NET and Azure App Service, with all examples and instructions tailored to ASP.NET Core and related Microsoft tooling. It references GitHub Codespaces and Azure CLI, which are cross-platform, but there are no explicit Linux-specific instructions, troubleshooting, or examples. The workflow and code samples are exclusively for .NET on App Service, with no mention of Linux hosting, deployment, or alternative frameworks. The documentation does not provide parity for Linux users or those using non-Windows environments beyond the implicit support via Codespaces.
Recommendations
- Add explicit instructions for running and deploying the sample app on Linux (e.g., Ubuntu) using local development environments, including package installation and environment setup.
- Include Linux shell (bash) command examples alongside or instead of generic 'codespace terminal' instructions, clarifying that all steps work on Linux as well as Windows.
- Mention and provide guidance for deploying to Azure App Service for Linux, not just the generic App Service, and clarify any differences.
- Provide troubleshooting tips for common Linux-specific issues (e.g., file permissions, case sensitivity, dependency installation).
- Reference alternative OpenAPI tools or libraries commonly used in Linux/.NET environments, if applicable.
- Ensure that all CLI commands (dotnet, azd) are shown in a way that is clearly cross-platform, and note any OS-specific prerequisites.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/app-service-web-tutorial-custom-domain.md
.../app-service/app-service-web-tutorial-custom-domain.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page is generally cross-platform and avoids explicit Windows or PowerShell bias in its main instructions. However, in the troubleshooting section, when suggesting how to clear the DNS cache, only the Windows-specific command ('ipconfig /flushdns') is mentioned, with no Linux or macOS equivalents. This presents a subtle 'windows_first' and 'missing_linux_example' bias.
Recommendations
- When providing troubleshooting steps involving system commands (such as clearing DNS cache), include equivalent commands for Linux (e.g., 'sudo systemd-resolve --flush-caches' or 'sudo resolvectl flush-caches') and macOS (e.g., 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder').
- Wherever possible, avoid mentioning only Windows tools or commands. If a platform-specific command is necessary, present all major OSes together or link to platform-specific instructions.
- Review other sections for similar implicit assumptions about the user's OS, and ensure parity in examples and troubleshooting guidance.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-cleanup.md
...main/articles/app-service/includes/tutorial-cleanup.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation only describes how to delete resources using the Azure portal, which is a graphical interface commonly associated with Windows environments. There are no examples or instructions for performing the same task using command-line tools such as Azure CLI or Bash, which are more commonly used in Linux environments. This omission may disadvantage Linux users or those who prefer automation and scripting.
Recommendations
- Add instructions and examples for deleting the resource group using Azure CLI (az group delete) with both Windows (PowerShell/CMD) and Linux (Bash) command syntax.
- Include sample commands for PowerShell and Bash side by side to ensure parity.
- Mention that the Azure portal is cross-platform, but also highlight command-line alternatives for users who prefer scripting or are on non-Windows systems.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/webjobs-create/webjobs-supported-platforms.md
...includes/webjobs-create/webjobs-supported-platforms.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation lists Windows hosting options and file/script types before their Linux equivalents, and Windows-specific tools and script types (.exe, .cmd, .bat, .ps1) are mentioned before Linux equivalents (.sh). This ordering and emphasis may suggest a Windows-centric perspective.
Recommendations
- Alternate the order of Windows and Linux hosting options, or list them alphabetically to avoid implicit prioritization.
- List script/file types in a neutral or grouped manner (e.g., by function or alphabetically), rather than placing Windows types first.
- Explicitly mention Linux tools and patterns (e.g., cron jobs, shell scripts) alongside Windows equivalents.
- Provide balanced examples for both Windows and Linux environments where applicable.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/includes/tutorial-microsoft-graph-as-app/introduction.md
...cludes/tutorial-microsoft-graph-as-app/introduction.md
Medium Priority
View Details →
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, but PowerShell is presented first and in more detail. The PowerShell example uses Windows-centric tooling and patterns, which may be more familiar to Windows users. There are no explicit Linux or Bash-specific examples, and the PowerShell script is more verbose and featured than the Azure CLI alternative.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell examples to avoid implicit Windows-first bias.
- Expand the Azure CLI example with more detailed comments and step-by-step explanations, matching the depth of the PowerShell example.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash shell snippets where appropriate.
- If PowerShell is required, clarify that PowerShell Core is cross-platform and provide installation instructions for Linux/macOS users.
- Consider adding a table or section that summarizes equivalent commands for Windows (PowerShell), Linux (Bash/Azure CLI), and macOS.
App Service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/tutorial-secure-domain-certificate.md
...cles/app-service/tutorial-secure-domain-certificate.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally avoids OS-specific instructions, but in the troubleshooting section for clearing DNS cache, it only provides a Windows-specific command (`ipconfig /flushdns`) and does not mention Linux or macOS equivalents. This presents a subtle Windows-first bias and omits guidance for users on other platforms.
Recommendations
- When providing troubleshooting steps like clearing DNS cache, include equivalent commands for Linux (e.g., `sudo systemd-resolve --flush-caches` or `sudo resolvectl flush-caches`) and macOS (e.g., `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`).
- Wherever possible, avoid OS-specific instructions unless all major platforms are covered equally.
- If screenshots or UI instructions are platform-agnostic (as in this case), ensure any command-line or troubleshooting advice is also cross-platform.
- Consider adding a note or table summarizing common DNS cache clearing commands for Windows, Linux, and macOS.