Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 926-950 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-powershell.md
...des/create-azure-managed-domain-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is traditionally associated with Windows environments. There are no examples or instructions for Linux or cross-platform command-line tools such as Azure CLI, nor is there mention of Bash or shell scripting alternatives. This creates a bias towards Windows users and may hinder Linux users or those on other platforms.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention that PowerShell Core is available on Linux and macOS, if relevant, and provide installation instructions or links.
- Reorder or parallelize examples so that both PowerShell and Azure CLI (or REST API) options are presented side-by-side or in clearly marked sections.
- Explicitly state platform compatibility for each tool and example.
- Include notes or links for Linux/macOS users on how to perform the same tasks.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-getstarted-portal.md
...ob/main//articles/dns/private-dns-getstarted-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively using Windows Server as the example VM OS, referencing RDP for access, and demonstrating DNS resolution via PowerShell scripts and Windows command prompt. There are no examples or instructions for creating or testing with a Linux VM, nor are Linux-native tools or shell commands (such as SSH, Bash, or dig) mentioned. The 'Run command' feature is demonstrated only with PowerShell, and the quickstart does not provide parity for Linux users.
Recommendations
- Include parallel instructions and screenshots for creating a Linux virtual machine (e.g., Ubuntu) alongside the Windows Server example.
- Demonstrate how to access the Linux VM using SSH instead of RDP.
- Provide examples of testing DNS resolution from a Linux VM using Bash commands such as 'ping', 'nslookup', or 'dig'.
- Show how to use the 'Run command' feature with Linux VMs (e.g., 'RunShellScript') and provide equivalent shell commands.
- Explicitly mention that the steps apply to both Windows and Linux VMs, and highlight any differences.
- Where PowerShell or Windows-specific tools are referenced, provide Linux equivalents or alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/chat/openai-chat-bot-integration.md
...rvices/quickstarts/chat/openai-chat-bot-integration.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Visual Studio Code (VS Code) and Azure App Service extension for deployment, with no mention of Linux-specific workflows or CLI alternatives. The deployment instructions assume a GUI-based, VS Code-centric workflow, which is more common on Windows. There are no examples or guidance for deploying from Linux terminals, using cross-platform CLI tools, or alternative editors. There is also an implicit assumption that the user is familiar with Windows-style application deployment patterns.
Recommendations
- Add explicit instructions for deploying the web app using the Azure CLI or Azure PowerShell, including command-line examples that work on Linux and macOS.
- Include alternative deployment steps for users who do not use VS Code, such as instructions for deploying directly from the terminal using 'az webapp deploy' or GitHub Actions.
- Mention that the 'dotnet publish' command is cross-platform, and provide any Linux/macOS-specific notes if necessary (e.g., path separators, prerequisites).
- Clarify that the Azure portal and all resource creation steps are accessible from any OS, and provide screenshots or notes that are not Windows-specific.
- If screenshots are OS-specific, consider including at least one example from a Linux or macOS environment, or use neutral imagery.
- Add a note or section on prerequisites for Linux/macOS users (e.g., installing .NET SDK, Azure CLI, etc.).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-resiliency.md
...docs/blob/main//articles/dns/private-dns-resiliency.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates bias towards Windows by linking only to a PowerShell-based getting started guide for creating a Private DNS zone, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI, Bash). There are no Linux-specific examples or cross-platform guidance, and the PowerShell path is presented as the default/only option.
Recommendations
- Include links to Linux-friendly guides, such as how to create a Private DNS zone using Azure CLI or Bash.
- Add cross-platform code examples (PowerShell and Azure CLI) when demonstrating tasks.
- Explicitly mention that tasks can be performed on both Windows and Linux, and provide parity in documentation paths.
- Where possible, use neutral language and tool references (e.g., 'using Azure CLI or PowerShell') rather than defaulting to Windows tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-powershell.md
...es/create-custom-managed-domain-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module for all tasks, without providing any examples or guidance for Linux or cross-platform alternatives such as Azure CLI, Bash, or REST API. This creates a strong Windows bias and may hinder users on Linux or macOS systems.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Mention and link to installation instructions for Azure CLI alongside the PowerShell module in the prerequisites.
- Where possible, include Bash script examples or REST API equivalents to further support non-Windows users.
- Clearly indicate that PowerShell Core is available cross-platform, but also clarify any limitations or differences when running on Linux/macOS.
- Reorder or parallelize examples so that Windows and Linux/macOS users are equally supported, rather than presenting only Windows-centric tools and workflows.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/send-email-async-sync-net.md
...uickstarts/email/includes/send-email-async-sync-net.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation is heavily focused on .NET/C# and provides instructions and examples that are platform-agnostic in terms of .NET Core, but the language used in terminal instructions and examples tends to mention Windows tools and shells (cmd, PowerShell) before Linux equivalents. There are no explicit Linux-specific instructions or examples, and no mention of Linux package managers or shell environments beyond a brief mention of Bash. The documentation assumes familiarity with Windows-first patterns and tools.
Recommendations
- Provide explicit Linux and macOS instructions alongside Windows, such as mentioning Linux shells (Bash, Zsh) and package managers (apt, yum, brew) where relevant.
- When referencing terminal or command windows, list Bash or Linux terminals first or equally (e.g., 'in a terminal (such as Bash, cmd, or PowerShell)').
- Include troubleshooting notes or environment setup tips for Linux (e.g., permissions, environment variable export syntax, .NET installation on Linux).
- Add sample commands for setting environment variables in Linux (e.g., 'export COMMUNICATION_SERVICES_CONNECTION_STRING=...') as well as Windows ('set ...').
- Where file paths or editors are referenced, provide cross-platform alternatives (e.g., 'edit Program.cs with your preferred editor, such as nano, vim, or Notepad').
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-az-cli.md
...ncludes/create-azure-managed-domain-resource-az-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by linking exclusively to the Windows installation instructions for Azure CLI, using the 'azurepowershell-interactive' code block type for all command examples, and omitting any explicit mention or examples for Linux or macOS users. There are no Linux-specific instructions or clarifications, and the documentation implicitly assumes a Windows/PowerShell environment.
Recommendations
- Provide links to Azure CLI installation instructions for all supported platforms (Windows, Linux, macOS), or use a platform-agnostic link.
- Use generic 'bash' or 'shell' code block types for CLI commands, or provide both PowerShell and Bash examples where appropriate.
- Explicitly state that the 'az' CLI commands work cross-platform and clarify any differences in usage or prerequisites for Linux/macOS users.
- Include notes or callouts for Linux/macOS users regarding authentication, environment setup, or command-line differences if any exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-sender-username-resource-powershell.md
...includes/create-sender-username-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and references the Azure Az PowerShell Module, which is traditionally associated with Windows environments. There are no examples or instructions for Linux or cross-platform CLI tools (such as Azure CLI), nor is there mention of Bash or other non-Windows shells. The documentation assumes the user is operating in a Windows/PowerShell environment, which may exclude or confuse Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all operations (login, module installation, resource creation, update, listing, and deletion).
- Explicitly mention that PowerShell Core is cross-platform, if PowerShell is required, and provide installation instructions for Linux/macOS.
- Add Bash or shell script examples where appropriate.
- Include a section or note clarifying cross-platform support and guiding non-Windows users to relevant tools.
- Reorder examples or provide parallel examples so that Linux/macOS users are not deprioritized.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/create-email-resource-powershell.md
...rts/email/includes/create-email-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and Windows-centric tooling (Az PowerShell module) for all examples and instructions. There are no CLI, Bash, or Linux-native examples or references. The documentation assumes the user is on Windows or using PowerShell, with no mention of cross-platform alternatives or guidance for Linux/macOS users.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that the Az PowerShell module can be used on Linux/macOS via PowerShell Core, or provide installation instructions for those platforms.
- Add Bash shell examples for common tasks, or at least note how Linux/macOS users can accomplish the same steps.
- Reorganize sections so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools.
- Include a note clarifying platform compatibility for all tools mentioned.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-dns-scenarios.md
...-docs/blob/main//articles/dns/private-dns-scenarios.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the 'Next steps' section, where the only example for creating a Private DNS zone links to a PowerShell-based guide, with no mention of Linux, Bash, or CLI alternatives. There are no explicit Linux or cross-platform command examples, and the documentation implicitly assumes a Windows-centric workflow.
Recommendations
- Provide equivalent examples and links for Azure CLI (cross-platform) and Bash scripts alongside PowerShell instructions.
- Ensure that any 'Get Started' or tutorial links include both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) options, or link to a page that offers both.
- Explicitly mention that Azure Private DNS zones can be managed from any platform, and provide guidance or links for Linux/macOS users.
- Review diagrams and scenario descriptions to ensure terminology and examples are platform-neutral where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/send-email-powershell.md
...es/quickstarts/email/includes/send-email-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All setup and usage instructions are provided exclusively for Azure PowerShell, with explicit references to 'Windows PowerShell' and no mention of Linux or cross-platform alternatives. There are no Bash, Azure CLI, or other non-Windows examples, and all tooling and command-line instructions assume a Windows environment.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention support for Linux and macOS, and provide setup instructions for these platforms.
- If PowerShell Core (pwsh) is supported on Linux/macOS, clarify this and provide examples for those environments.
- Include Bash or shell script examples where appropriate, especially for common tasks like checking prerequisites or sending emails.
- Avoid language such as 'In a windows PowerShell' unless the feature is truly Windows-only; otherwise, use 'in PowerShell' and clarify cross-platform compatibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/includes/send-email-net.md
...-services/quickstarts/email/includes/send-email-net.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows (such as cmd and PowerShell) before mentioning Bash, and by omitting Linux-specific instructions or examples. All code and terminal instructions are generic but implicitly assume a Windows environment, with no explicit guidance for Linux users. There are no Linux-specific troubleshooting tips, environment setup, or alternative commands, and the sample code is exclusively for .NET/C# (a stack more common on Windows).
Recommendations
- Explicitly mention both Windows and Linux (and macOS) in all terminal/command instructions. For example, clarify that 'cmd, PowerShell, or Bash' are available on different platforms.
- Provide Linux/macOS-specific setup and troubleshooting steps, such as installing .NET on Ubuntu or using bash/zsh shells.
- Include sample commands for common Linux distributions (e.g., apt-get install dotnet-sdk-7.0) and macOS (e.g., brew install dotnet).
- Add notes about file path conventions and environment variable setting for Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...).
- Offer sample code or quickstarts in additional languages commonly used on Linux (e.g., Python, Node.js) if available.
- Ensure all screenshots, if any, are cross-platform or provide both Windows and Linux/macOS versions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/events/includes/register-provider-powershell.md
...starts/events/includes/register-provider-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides PowerShell commands for registering the Event Grid resource provider, which are specific to Windows environments. There are no examples or instructions for Linux or cross-platform tools such as Azure CLI, and Windows tooling is implicitly prioritized.
Recommendations
- Add equivalent Azure CLI commands (e.g., 'az provider register --namespace Microsoft.EventGrid') for cross-platform and Linux users.
- Present both PowerShell and CLI examples side by side or clearly indicate which platforms each applies to.
- Explicitly mention that PowerShell examples are for Windows and provide Bash or shell examples for Linux/macOS.
- Consider listing Azure CLI (cross-platform) examples first or in parallel to avoid Windows-first bias.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-powershell.md
...ail-advanced/includes/inline-attachments-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use PowerShell syntax, and the only installation instructions reference Azure PowerShell for Windows. There are no examples or guidance for Linux or cross-platform command-line environments (such as Bash or Azure CLI). The prerequisite check explicitly mentions 'windows powershell', and there is no mention of equivalent steps for Linux or macOS users.
Recommendations
- Provide equivalent instructions and examples using Azure CLI, which is cross-platform and works on Windows, Linux, and macOS.
- Include Bash or shell script examples for Linux/macOS users, especially for file handling and sending emails.
- Clarify that Azure PowerShell can be installed and used on Linux/macOS, and provide installation links and instructions for those platforms.
- Avoid language that assumes the user is on Windows (e.g., 'In a windows powershell...'). Instead, use neutral phrasing or provide platform-specific sections.
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email.md
...communication-services/quickstarts/email/send-email.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page includes a dedicated section and example for Azure PowerShell, a Windows-centric tool, and lists it as a primary platform pivot alongside Azure CLI, Portal, and programming languages. There is no mention of Linux-specific tools or shell examples (e.g., Bash), and PowerShell is given parity with cross-platform or platform-agnostic approaches, which may suggest a Windows-first or PowerShell-heavy bias.
Recommendations
- Add explicit Bash or Linux shell examples where command-line usage is demonstrated, especially for common tasks like sending emails or cleaning up resources.
- Clarify that Azure PowerShell is cross-platform, but also provide equivalent Bash/Azure CLI examples side-by-side where possible.
- Ensure that Linux and macOS users are addressed in troubleshooting and setup instructions, not just Windows/PowerShell users.
- Consider reordering pivots or examples so that platform-agnostic or cross-platform tools (like Azure CLI) are presented before Windows-specific tools (like PowerShell).
- Include a note or section for Linux users, highlighting any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp.md
...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a dedicated section for sending email using Windows PowerShell, but does not include equivalent Linux or cross-platform command-line examples (such as using sendmail, mailx, or mutt). The focus on PowerShell and lack of Linux-native tooling or shell script examples indicates a Windows-centric bias.
Recommendations
- Add a section demonstrating how to send email via SMTP using common Linux command-line tools (e.g., sendmail, mailx, mutt, or swaks).
- Include Bash or shell script examples for sending email with SMTP to ensure parity with the PowerShell example.
- Clearly indicate which examples are cross-platform and which are Windows-specific, and provide equivalent Linux/macOS instructions wherever possible.
- Consider including Python or other scripting language examples that work on both Windows and Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-powershell.md
...send-email-smtp/includes/send-email-smtp-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides instructions and examples using PowerShell and the Windows-specific Send-MailMessage cmdlet. There are no examples or guidance for sending email via SMTP from Linux or cross-platform environments, nor are alternative tools (such as sendmail, mailx, or Python scripts) mentioned. This creates a strong Windows and PowerShell bias, making it less accessible for Linux or macOS users.
Recommendations
- Add equivalent Linux examples using common tools such as sendmail, mailx, or mutt.
- Provide a cross-platform example using a scripting language like Python (e.g., using smtplib) to demonstrate SMTP email sending.
- Explicitly mention that the instructions are for Windows/PowerShell, and provide parallel instructions for Linux/macOS users.
- Reference Linux documentation or external resources for SMTP email sending.
- Consider restructuring the documentation to present both Windows and Linux approaches side by side, or clearly label sections by platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/events/subscribe-to-events.md
...ion-services/quickstarts/events/subscribe-to-events.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by explicitly including PowerShell and .NET SDK examples, both of which are traditionally Windows-centric. There is no mention of Linux-specific tools or shell environments (such as Bash), and the CLI example is not clarified as cross-platform. The ordering of pivots places PowerShell and .NET alongside CLI and portal, but does not provide parity for Linux-native workflows or scripting environments.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide Bash or shell script examples where appropriate.
- Add a section or pivot for Linux shell (Bash) usage, demonstrating equivalent commands and workflows.
- Clarify that .NET SDK examples can be run on Linux, or provide alternative SDK examples (such as Python or JavaScript) that are popular in Linux environments.
- Balance the order of pivots so that Windows-specific tools (PowerShell, .NET) do not appear to be prioritized over cross-platform or Linux-native options.
- Where PowerShell is mentioned, consider also providing Bash equivalents for common automation tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-cli.md
...ity/includes/active-directory/service-principal-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively linking to 'Windows VM' versions of setup guides for managed identities (portal, PowerShell, CLI, ARM template, SDK), without mentioning or linking to Linux VM equivalents. There are no Linux-specific instructions or examples for setting environment variables or using the Azure CLI on Linux, and Windows tools and patterns (such as Visual Studio) are referenced without Linux alternatives.
Recommendations
- Provide parallel links and instructions for configuring managed identities on Linux VMs, not just Windows VMs.
- Include Linux-specific examples for setting environment variables (e.g., export commands for Bash) alongside or before Windows/PowerShell examples.
- Mention cross-platform development environments (such as VS Code) and provide guidance for Linux users, not just Visual Studio.
- Ensure that all referenced articles or quickstarts have both Windows and Linux variants, or clarify when instructions are cross-platform.
- Explicitly state when steps are the same for both Windows and Linux, or highlight differences as needed.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/events/includes/create-event-subscription-powershell.md
...vents/includes/create-event-subscription-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell (Az module) commands and examples, which are most commonly associated with Windows environments. There are no examples or guidance for using equivalent Azure CLI commands, Bash scripts, or Linux-native tools. The prerequisites and all operational steps assume PowerShell usage, which may disadvantage Linux or cross-platform users.
Recommendations
- Provide equivalent Azure CLI examples for all operations (create, list, update, delete event subscriptions), as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and provide installation instructions for non-Windows platforms.
- Add Bash script examples or note how to adapt the commands for Bash/Unix shells where appropriate.
- Reorganize the documentation to present cross-platform (CLI) solutions first or alongside PowerShell, rather than PowerShell-only instructions.
- Update the prerequisites to include installation instructions for Azure CLI and/or PowerShell Core on Linux/macOS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/router/job-router-azure-openai-integration.md
...ckstarts/router/job-router-azure-openai-integration.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing Visual Studio Code and its Azure Functions extension for setup and deployment, with no mention of Linux-specific workflows or CLI alternatives. All setup and deployment steps are described using GUI-based tools common on Windows, and there are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform terminal commands).
Recommendations
- Include instructions for deploying and managing Azure Functions using the Azure CLI and/or Azure Functions Core Tools, which are cross-platform and commonly used on Linux.
- Provide alternative steps for Linux users, such as using terminal commands to set environment variables, deploy function apps, and update configuration files.
- Add explicit notes or sections highlighting Linux/macOS compatibility, and ensure that all steps can be performed on non-Windows platforms.
- Where screenshots are provided, consider including at least one example from a Linux terminal or a cross-platform tool.
- Mention that Visual Studio Code is cross-platform, but also provide guidance for users who may prefer not to use a GUI or who are working in headless/server environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/includes/create-resource-powershell.md
...ces/quickstarts/includes/create-resource-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively uses PowerShell commands and Windows-centric tools (Az PowerShell Module) for all examples and instructions. There are no examples or guidance for Linux users, such as using Azure CLI or Bash. The documentation assumes the use of PowerShell, which is more common on Windows, and does not mention or provide parity for Linux environments.
Recommendations
- Add equivalent Azure CLI (az) command examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux.
- Include instructions for installing and using the Azure CLI on Linux and macOS, alongside the PowerShell module.
- Present both PowerShell and CLI examples side by side, or clearly indicate which sections are for Windows/PowerShell and which are for Linux/CLI.
- Avoid assuming the user is on Windows or using PowerShell by default; mention cross-platform options early in the prerequisites.
- Link to Linux/macOS-specific documentation where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/includes/telemetry-app-insights-net.md
...ces/quickstarts/includes/telemetry-app-insights-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by referencing 'cmd' and 'PowerShell' before 'Bash' when suggesting console windows, and does not provide any Linux- or macOS-specific instructions or examples. All command-line instructions are generic but lack explicit Linux/macOS context, such as environment variable setting or file editing. There are no Linux-specific tools, patterns, or troubleshooting notes, and the documentation assumes familiarity with Windows conventions.
Recommendations
- When listing console options, alternate the order or explicitly mention Linux/macOS terminals (e.g., 'Bash, Terminal, cmd, or PowerShell').
- Provide Linux/macOS-specific instructions for setting environment variables (e.g., 'export VAR=value' for Bash) alongside Windows examples.
- Include notes about editing files or running commands on Linux/macOS (e.g., using 'nano', 'vim', or 'open' instead of 'notepad').
- Add troubleshooting tips or links relevant to Linux/macOS users, such as permissions or path issues.
- Ensure that all steps are clearly cross-platform, or provide parallel instructions where platform differences exist.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/manage-teams-identity.md
...nication-services/quickstarts/manage-teams-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a bias toward Windows environments by providing only PowerShell commands and instructions for administrative tasks (such as creating service principals), with no mention of Linux or cross-platform alternatives. The troubleshooting and setup steps assume the use of PowerShell and Windows-specific tooling, and there are no Bash, Azure CLI, or cross-platform command examples. This may hinder Linux or macOS users attempting to follow the guide.
Recommendations
- Provide equivalent instructions and command examples using Azure CLI and/or Bash scripts for Linux/macOS users alongside PowerShell commands.
- Explicitly mention that PowerShell Core is cross-platform, or provide guidance for installing and using PowerShell on Linux/macOS if PowerShell is required.
- Where possible, use Azure Portal or REST API instructions as alternatives to platform-specific command-line tools.
- Ensure that all code snippets and troubleshooting steps have Linux/macOS equivalents, and clarify any platform-specific requirements.
- Add a note at the start of the documentation indicating which steps are platform-specific and provide links to cross-platform alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/private-resolver-hybrid-dns.md
...blob/main//articles/dns/private-resolver-hybrid-dns.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-based tools and workflows. PowerShell is highlighted as a primary automation method, and the only detailed example for configuring on-premises DNS conditional forwarders uses a Windows DNS server. There are no explicit examples or guidance for Linux-based DNS servers (such as BIND), nor are Linux command-line tools or configuration files referenced. The documentation assumes a Windows-centric environment for on-premises DNS integration.
Recommendations
- Add parallel examples for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND/named.conf).
- Include CLI commands and configuration file snippets for Linux environments alongside PowerShell and Windows GUI instructions.
- Explicitly mention that both Windows and Linux DNS servers are supported, and provide links or references to Linux-specific documentation.
- Balance the order of presentation so that Linux and Windows examples are given equal prominence, or alternate which is presented first.
- Where PowerShell is referenced, also provide Bash/Azure CLI equivalents for Linux administrators.