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 901-925 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/interop/tpe/teams-phone-extensibility-overview.md
...epts/interop/tpe/teams-phone-extensibility-overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as the use of PowerShell cmdlets and the Teams Admin Center (TAC portal), without mentioning or providing equivalent Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or references to CLI tools commonly used on Linux, and all administrative guidance assumes a Windows environment.
Recommendations
- Provide Linux-compatible instructions for Teams administration tasks, such as using the Microsoft Teams CLI or Azure CLI where possible.
- Include examples for both PowerShell (Windows) and Bash (Linux/macOS) when referencing command-line operations.
- Mention cross-platform tools and interfaces (such as the Teams Admin Center web portal) explicitly as being accessible from any OS.
- Clarify when features or administrative actions are available via web, CLI, or REST API, and provide links or examples for each.
- Add a section or note highlighting cross-platform support and any limitations for Linux or macOS users.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-sdk.md
...softDocs/azure-docs/blob/main//articles/dns/dns-sdk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Visual Studio and NuGet Package Manager (GUI) as the primary development environment and toolchain, with no mention of Linux-compatible alternatives or CLI-based workflows. The instructions for creating a service principal link to a PowerShell-based guide, and there are no examples or guidance for Linux users (e.g., using VS Code, .NET CLI, or Azure CLI).
Recommendations
- Include instructions for installing the required NuGet packages using the .NET CLI (dotnet add package ...) for cross-platform compatibility.
- Mention and provide examples for using VS Code or other cross-platform editors, not just Visual Studio.
- Provide alternative instructions for creating a service principal using Azure CLI (az ad sp create-for-rbac) instead of only linking to PowerShell-based guides.
- Clarify that the .NET SDK and sample project can be used on Linux and macOS, not just Windows.
- Ensure that all steps (project setup, authentication, package installation) have Linux/macOS equivalents or are written in a platform-agnostic way.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/pricing/teams-interop-pricing.md
...ion-services/concepts/pricing/teams-interop-pricing.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias. Teams desktop client is referenced repeatedly without specifying platform parity, and in scenario examples, the desktop client is implicitly associated with Windows. The only explicit desktop OS mentioned is Windows ("Windows, Chrome browser"), and PowerShell cmdlets are referenced for administrative tasks without Linux alternatives. There are no explicit Linux desktop client mentions or Linux administrative guidance.
Recommendations
- Explicitly mention that Teams desktop client is available on both Windows and Linux (and Mac), and provide examples or notes for Linux users.
- When referencing administrative tasks (e.g., assigning Teams Phone licenses), provide equivalent instructions or links for Linux/macOS environments, or clarify if PowerShell Core is supported cross-platform.
- In scenario examples, vary the OS context (e.g., include a user on Linux desktop client or using a Linux browser) to reflect cross-platform usage.
- If certain features or tools are Windows-only, clearly state this and suggest alternatives or workarounds for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-web-sites-custom-domain.md
...blob/main//articles/dns/dns-web-sites-custom-domain.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation is heavily biased toward Windows and PowerShell users. All command-line examples use Azure PowerShell cmdlets, with no mention or examples of equivalent Azure CLI (cross-platform) or Bash commands. The DNS query example uses nslookup in a Windows PowerShell prompt, with no reference to dig or other common Linux tools. The overall flow assumes a Windows environment, with no guidance for Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI (az) command examples alongside or in place of PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include DNS query examples using dig (e.g., dig www.contoso.com) in addition to nslookup, and clarify that both tools are available on different platforms.
- Avoid using Windows-specific prompt notation (e.g., PS C:\>) unless also showing Linux/macOS shell equivalents.
- Explicitly mention that all steps can be performed on Linux/macOS, and provide any necessary platform-specific notes (such as installing Azure CLI or dig).
- Consider reordering examples or providing tabs to let users select their preferred platform (Windows/PowerShell, Linux/Bash, macOS/Terminal).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/concepts/voice-video-calling/manage-call-quality.md
...es/concepts/voice-video-calling/manage-call-quality.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in the 'Prepare your network and prioritize important network traffic by using QoS' section, where it references Windows Group Policy objects and does not mention Linux equivalents or provide Linux-specific guidance. There are no PowerShell-heavy examples, but Windows tools and patterns are mentioned exclusively or first, and there is a lack of Linux examples or parity in network configuration guidance.
Recommendations
- Include Linux-specific instructions or references for implementing QoS, such as using 'tc', 'iptables', or other Linux traffic control tools.
- When mentioning Windows Group Policy, also mention equivalent Linux approaches or link to relevant Linux documentation.
- Provide cross-platform examples or explicitly state if a feature or recommendation is Windows-only.
- Review other sections for opportunities to add Linux/macOS-specific troubleshooting or configuration steps, especially where native platform logging or diagnostics are discussed.
- Ensure that all tooling and configuration recommendations are inclusive of major supported platforms, or clearly indicate any platform limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-js.md
...l-automation/includes/audio-streaming-quickstart-js.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily by referencing Windows first in resource creation links (with '?tabs=windows' in URLs), and by linking to a WebSockets guide specifically for 'Windows Azure Web Sites'. There are no Linux-specific examples, tools, or setup instructions, and no mention of Linux or cross-platform considerations in the setup or troubleshooting sections.
Recommendations
- Provide platform-agnostic links or ensure that documentation links include tabs or pivots for Linux and macOS, not just Windows.
- Include explicit Linux (and optionally macOS) setup instructions or examples, especially for creating Azure Communication Services resources and setting up WebSocket servers.
- Reference cross-platform or Linux-specific documentation for WebSockets and related server setup, rather than only Windows-focused guides.
- Review all quickstart and resource links to ensure parity across operating systems, and avoid defaulting to Windows in URLs or examples.
- Add a note clarifying that the JavaScript and Node.js code is cross-platform, and provide troubleshooting tips for common Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/call-automation/includes/audio-streaming-quickstart-python.md
...tomation/includes/audio-streaming-quickstart-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits Windows bias primarily in the prerequisites and resource links. The link to creating an Azure Communication Services resource includes a 'tabs=windows' parameter, suggesting a Windows-first approach. The reference for learning about WebSockets points to a Windows Azure-specific blog post, and there are no Linux-specific instructions or examples. No Linux or cross-platform guidance is provided for setting up the environment or running the Python code, and there are no mentions of Linux tools or commands.
Recommendations
- Provide Linux-specific or cross-platform instructions and links alongside or before Windows-specific ones.
- Update the 'Create an Azure Communication Services resource' link to either default to a neutral tab or include both Windows and Linux tabs.
- Include references to cross-platform or Linux-specific WebSocket server setup guides, not just Windows Azure resources.
- Explicitly state that the Python code samples are cross-platform and provide any necessary Linux-specific setup notes (e.g., package installation, firewall configuration).
- Ensure all external documentation links are either cross-platform or have clear Linux equivalents.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-reverse-dns-for-azure-services.md
...in//articles/dns/dns-reverse-dns-for-azure-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell and classic PowerShell examples, using Windows-specific tools and cmdlets, and omitting Linux-native command-line examples (such as Bash or shell scripting). While Azure CLI is cross-platform, the documentation does not provide explicit Linux shell or scripting guidance, nor does it mention Linux tools for DNS validation or troubleshooting. PowerShell examples are consistently presented first, reinforcing a Windows-centric workflow.
Recommendations
- Add explicit Bash/shell command examples for all Azure CLI operations, demonstrating usage in a Linux environment.
- Include Linux-native DNS troubleshooting tools (e.g., dig, host, nslookup) to validate reverse DNS records after configuration.
- Alternate the order of examples (e.g., sometimes present Azure CLI before PowerShell) to avoid reinforcing a Windows-first workflow.
- Clarify that Azure CLI commands are cross-platform and provide sample shell scripts for automation on Linux.
- Where PowerShell is used for Cloud Services (which currently has no CLI support), acknowledge the lack of Linux-native options and suggest workarounds or feature requests.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/calling-sdk/breakoutrooms.md
...nication-services/how-tos/calling-sdk/breakoutrooms.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references Windows-specific tools (PowerShell) for Teams policy management and links to PowerShell-based documentation without mentioning or providing Linux/macOS alternatives. There are no Linux or cross-platform command-line examples or guidance, and Windows is the only desktop OS mentioned in the SDK support table, with no mention of Linux support.
Recommendations
- Provide equivalent Linux/macOS instructions for managing Teams meeting policies, such as using Microsoft Graph API or cross-platform CLI tools.
- Where PowerShell is referenced, clarify if the commands can be run on PowerShell Core (available on Linux/macOS) or provide alternative methods.
- In SDK support tables, explicitly state Linux support status for parity and transparency.
- Include examples or links for Linux/macOS users where administrative or development tasks are described.
- Avoid assuming Windows as the default platform; present cross-platform options where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/cte-calling-sdk/shared-line-appearance.md
...ices/how-tos/cte-calling-sdk/shared-line-appearance.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Teams PowerShell for delegate assignment without mentioning Linux or cross-platform alternatives. The prerequisites list Teams PowerShell as a method for configuration, and there are no examples or instructions for Linux users. The support table includes a 'Windows' column but omits explicit Linux support, and there are no Linux-specific tools or command-line examples provided.
Recommendations
- Include Linux-compatible instructions or alternatives for assigning delegates, such as using Teams web client or REST APIs if available.
- Clarify whether PowerShell commands can be run on PowerShell Core on Linux/macOS, and provide installation guidance if so.
- Add a support matrix row or note for Linux to clarify platform compatibility.
- Ensure that examples and tooling references are cross-platform or provide parity for Linux users.
- Explicitly mention any limitations or workarounds for Linux users in the prerequisites and setup steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/how-tos/telephony/domain-validation.md
...cation-services/how-tos/telephony/domain-validation.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides a DNS verification example using the Windows-specific nslookup command, referencing the Windows command documentation and omitting equivalent Linux/macOS instructions. No Linux or cross-platform alternatives are mentioned, and the Windows tool is presented as the default approach.
Recommendations
- Include Linux/macOS equivalents for DNS verification, such as referencing the nslookup or dig commands available on those platforms.
- Avoid linking exclusively to Windows command documentation; provide cross-platform or OS-specific links as appropriate.
- Present examples for both Windows and Linux/macOS, or use cross-platform language (e.g., 'You can use nslookup or dig to verify DNS propagation').
- Consider a table or note that lists commands for different operating systems to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-reverse-dns-hosting.md
...ocs/blob/main//articles/dns/dns-reverse-dns-hosting.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and includes PowerShell-specific instructions and screenshots. There is a strong emphasis on PowerShell usage throughout, which may suggest a Windows-first approach. While Azure CLI is cross-platform and included, there are no Linux shell-specific examples or references, and no mention of Linux-native tools or workflows. The documentation does not provide parity in terms of Linux command-line usage or guidance for Linux administrators.
Recommendations
- Provide Linux shell (bash) command examples where appropriate, especially for DNS-related tasks that could be performed outside Azure CLI.
- Include explicit notes that Azure CLI commands work identically on Linux, macOS, and Windows, and consider demonstrating usage in a Linux terminal.
- Balance the order of examples by sometimes presenting Azure CLI before PowerShell, or grouping them together without a clear preference.
- Reference Linux-native DNS tools (such as dig, nslookup, or host) for verification steps, and provide example commands for checking DNS records from a Linux environment.
- Add screenshots or terminal outputs from Linux environments to illustrate cross-platform compatibility.
- Clarify that Azure PowerShell is available on non-Windows platforms, but that Azure CLI is often preferred for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-python.md
...d-messaging/whatsapp/includes/common-setting-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently provides only Windows-specific instructions for setting environment variables (using 'setx'), and references Windows tools and workflows (such as Visual Studio) without mentioning Linux or macOS equivalents. There are no examples or guidance for users on Linux or macOS platforms, which may hinder cross-platform usability.
Recommendations
- Provide equivalent Linux/macOS instructions for setting environment variables (e.g., using 'export' in bash or zsh).
- Include cross-platform notes or tabs for environment variable setup, with commands for Windows (setx), Linux/macOS (export), and possibly PowerShell.
- Mention popular cross-platform editors (such as VS Code) in addition to or instead of Windows-only tools like Visual Studio.
- Add a section or callout explicitly stating that the SDK and instructions are cross-platform, with links to platform-specific setup guides if available.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/get-started/messages-get-started-net.md
...tsapp/includes/get-started/messages-get-started-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing Windows-specific tools (Visual Studio) and providing instructions for compiling and running code using Windows-centric shortcuts and workflows before mentioning cross-platform alternatives. There is a lack of explicit Linux/macOS guidance, and no Linux-specific examples or terminal instructions are provided.
Recommendations
- Explicitly mention that Visual Studio Code and .NET CLI are cross-platform and can be used on Linux/macOS as well as Windows.
- Provide Linux/macOS-specific instructions for building and running .NET applications (e.g., using terminal commands on bash/zsh, or referencing common Linux package managers for .NET installation).
- Add a note or section clarifying that all code examples are platform-agnostic and can be run on any OS supported by .NET.
- If referencing Visual Studio, clarify that it is primarily for Windows, and suggest Visual Studio Code or JetBrains Rider as cross-platform alternatives.
- Include screenshots or terminal output examples from Linux/macOS environments to reinforce parity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/authenticate-notification-messages-client-net.md
...ludes/authenticate-notification-messages-client-net.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently uses Windows-specific commands (setx) for setting environment variables and references Windows tools (Visual Studio) as the primary or only example. There are no Linux or macOS equivalents provided for setting environment variables or for common developer workflows, which may hinder users on non-Windows platforms.
Recommendations
- Provide Linux/macOS equivalents for all environment variable commands (e.g., export VAR=value for bash/zsh).
- Include notes or tabs for both Windows and Linux/macOS in all setup instructions.
- Mention cross-platform editors (such as VS Code) alongside or instead of Windows-only tools like Visual Studio.
- Link to official documentation for setting environment variables on different operating systems.
- Review all code and command snippets to ensure parity and clarity for users on all major platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/mqtt-certificate-chain-client-authentication.md
...t-grid/mqtt-certificate-chain-client-authentication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides certificate generation instructions and examples exclusively for Windows users using PowerShell, without offering equivalent Linux or cross-platform command examples. The guidance explicitly references Windows and PowerShell, and does not mention or demonstrate how to perform these steps on Linux or macOS, despite using a cross-platform tool (step CLI).
Recommendations
- Provide equivalent certificate generation and management instructions for Linux and macOS, using bash or shell commands.
- Present cross-platform examples first, or in parallel, rather than focusing on Windows/PowerShell.
- Avoid language such as 'in Windows PowerShell, run...' when the tool is cross-platform; instead, offer both Windows and Linux/macOS command syntax.
- Add notes or sections clarifying any OS-specific differences in file paths, command syntax, or prerequisites.
- Where screenshots or UI instructions are given, clarify if there are any differences for Linux/macOS users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-traffic-log-how-to.md
...docs/blob/main//articles/dns/dns-traffic-log-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing extensive PowerShell-based automation and scripting examples, referencing Windows file paths (e.g., C:\bin\PSRepo), and using Windows-specific tools (PowerShell cmdlets, Resolve-DnsName). There are no equivalent CLI, Bash, or Linux-native examples for creating or managing DNS security policies, nor are there instructions for using the Azure CLI or Linux shell environments. The only command-line DNS query example uses the Windows command prompt (C:\>dig), but does not clarify Linux usage or syntax differences.
Recommendations
- Add equivalent Azure CLI (az) examples for all resource creation, configuration, and management steps, including DNS security policy, domain lists, and diagnostic settings.
- Provide Bash shell scripts or Linux command-line examples alongside PowerShell, especially for resource automation.
- When showing DNS query examples, clarify that 'dig' is available on both Windows and Linux, and provide sample Linux shell prompts (e.g., $ dig ...).
- Reference Linux file paths and environment variables where appropriate, or provide cross-platform notes.
- Include instructions for installing and using required tools (e.g., dig, Azure CLI) on Linux.
- Balance the order of presentation: do not always present PowerShell/Windows first; consider parallel tabbed sections for PowerShell and CLI/Bash.
- Explicitly mention that all features are available cross-platform, or note any limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/download-media/download-media-net.md
...whatsapp/includes/download-media/download-media-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing file path examples using Windows-style paths (e.g., c:\temp\media.jpg), referencing Windows-specific tools (Visual Studio), and omitting explicit Linux/macOS equivalents for file paths, file handling, and development environment setup. There are no Linux or cross-platform file path examples, and the build/run instructions do not mention Linux-specific considerations.
Recommendations
- Provide file path examples using both Windows (e.g., c:\temp\media.jpg) and Linux/macOS (e.g., /tmp/media.jpg) formats.
- Explicitly mention that Visual Studio Code and .NET CLI are cross-platform, and provide any Linux/macOS-specific instructions if needed.
- Include notes or code comments about file permissions and directory existence on Linux/macOS.
- Add a section or tab for running the code on Linux/macOS, including terminal commands and any environment setup differences.
- Avoid assuming Windows as the default environment in examples and instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/templates/template-messages-quick-reference-net.md
...des/templates/template-messages-quick-reference-net.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Dotnet Only
Summary
The documentation is heavily focused on .NET and Windows-centric development environments. All code samples are in C# for .NET, and the only build/run instructions are for .NET CLI, Visual Studio, and Visual Studio Code. There are no Linux-specific instructions, nor are there any references to Linux tools, shell commands, or alternative SDKs (e.g., Python, Java, Node.js). The documentation assumes the user is developing on Windows or using .NET, which may exclude or inconvenience Linux users and those using other programming languages.
Recommendations
- Add explicit instructions for Linux users, such as how to install the .NET SDK on common Linux distributions and how to build/run .NET projects from the Linux terminal.
- Include alternative code samples or references for other supported SDKs (e.g., Python, Java, JavaScript/Node.js) if available.
- When listing build/run instructions, provide parity for Linux/macOS (e.g., shell commands, VS Code on Linux) and clarify any OS-specific steps.
- Avoid assuming Visual Studio is the default IDE; mention cross-platform editors like VS Code and JetBrains Rider, and provide relevant instructions.
- If any steps require Windows-only tools or behaviors, explicitly note this and provide Linux/macOS alternatives where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/python-application-setup.md
...essaging/whatsapp/includes/python-application-setup.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides a Windows-specific command ('type nul > messages-quickstart.py') for creating a new Python file, without offering an equivalent Linux/macOS example (such as 'touch messages-quickstart.py'). This may confuse or exclude users on non-Windows platforms.
Recommendations
- Provide both Windows and Linux/macOS commands for file creation, e.g., 'type nul > messages-quickstart.py' (Windows) and 'touch messages-quickstart.py' (Linux/macOS).
- Wherever possible, use cross-platform commands or clearly indicate platform-specific instructions.
- Review other steps to ensure parity and clarity for users on all major operating systems.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dnssec-how-to.md
...cs/azure-docs/blob/main//articles/dns/dnssec-how-to.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed PowerShell examples, referencing Windows-specific tools (e.g., dig.exe), and omitting explicit Linux/Bash examples. The CLI section uses Azure CLI, which is cross-platform, but sample commands and tool references (like dig.exe) are Windows-centric. There are no Linux shell or Bash examples, and the documentation does not mention Linux-specific patterns or tools, nor does it clarify cross-platform compatibility for commands.
Recommendations
- Add explicit Linux/Bash shell examples for all command-line steps, especially for obtaining DS records and using tools like dig (e.g., show 'dig' usage in Linux, not just 'dig.exe').
- Replace references to 'dig.exe' with 'dig', and clarify that 'dig' is available on both Windows and Linux, providing installation instructions if needed.
- In CLI sections, show both Windows (cmd/PowerShell) and Linux (bash) command syntax where differences exist.
- Ensure that any PowerShell-specific instructions are accompanied by equivalent Bash or Linux shell instructions.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide links to installation guides for each OS.
- Where screenshots or UI steps are shown, clarify that the Azure Portal is OS-agnostic.
- Review the order of examples: consider presenting cross-platform or Linux examples before or alongside Windows/PowerShell examples to avoid 'windows_first' bias.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-python.md
...tart-make-an-outbound-call-using-callautomation-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows mild Windows bias by referencing Visual Studio and Visual Studio Code as the primary (and only) editors/IDEs for running the code, with explicit instructions for Visual Studio (a Windows-centric tool). There are no explicit Linux/macOS instructions or examples for running the application, and no mention of alternative editors or terminal usage outside the Microsoft ecosystem. The documentation does not provide PowerShell-specific commands, but the overall workflow and tool recommendations are Windows-centric.
Recommendations
- Add explicit instructions for running the application on Linux and macOS, such as using the terminal or alternative editors (e.g., PyCharm, Sublime Text, or simply the command line).
- Include a generic command-line example for running the Python application (e.g., `python main.py`) outside of the Visual Studio/VS Code context.
- Mention cross-platform editors and tools, and clarify that the sample code and setup steps are platform-agnostic.
- If referencing Visual Studio, clarify that it is primarily for Windows and suggest alternatives for other platforms.
- Consider adding a section or note about verifying Python and pip installation on Linux/macOS, and any OS-specific dependencies or troubleshooting tips.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/email/add-custom-verified-domains.md
...vices/quickstarts/email/add-custom-verified-domains.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by explicitly including PowerShell as a primary platform, referencing Windows-based DNS management, and linking to guides that are Windows-centric. There is no mention of Linux-specific tools or shell commands for DNS management or domain verification, and the 'Other (General)' DNS guide points to a Windows-based DNS article. Linux users are not provided with parity in examples or guidance.
Recommendations
- Add explicit Linux/Bash examples for domain verification and DNS record management, such as using dig, nsupdate, or editing BIND zone files.
- Include links to cross-platform or Linux-specific DNS management documentation in the 'Other (General)' section, not just Windows-based DNS.
- Ensure parity in the platform pivots by providing clear, step-by-step instructions for Linux environments alongside PowerShell and Azure CLI.
- Reference Linux-native tools and workflows (e.g., using nano/vim to edit zone files, systemd-resolved, or web-based DNS panels common on Linux servers).
- Where PowerShell is mentioned, clarify if Azure CLI or REST API alternatives are available and provide those examples.
- Avoid defaulting to Windows-based terminology or tools in general guidance sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/chat/quickstart-botframework-integration.md
...uickstarts/chat/quickstart-botframework-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references Visual Studio (a Windows-centric IDE), .NET Core, and C# for all code samples and deployment steps. All instructions for building, running, and deploying the bot and chat app are given using Visual Studio and Windows-specific workflows, with no mention of Linux or cross-platform alternatives. Package installation is shown using PowerShell syntax, and there are no CLI or editor-agnostic instructions. There are no Linux/macOS-specific notes, nor are there alternative examples using cross-platform tools or languages.
Recommendations
- Provide equivalent instructions for Linux and macOS users, including how to install .NET Core, use the dotnet CLI, and deploy without Visual Studio.
- Include examples using cross-platform editors (e.g., VS Code) and command-line tools for building and deploying the bot and chat app.
- Show package installation using the generic dotnet CLI (e.g., 'dotnet add package ...') rather than PowerShell-specific syntax.
- Add notes or sections on how to run and debug the sample projects on Linux/macOS, including any prerequisites or differences.
- Where screenshots or UI steps are shown for Visual Studio, provide CLI alternatives or screenshots from cross-platform tools.
- Consider including code samples in additional languages supported by Azure Communication Services (e.g., JavaScript/Node.js) to broaden accessibility.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/communication-services/quickstarts/create-communication-resource.md
...-services/quickstarts/create-communication-resource.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows some Windows bias. Windows and PowerShell are prioritized in several places: the Azure CLI installation link defaults to Windows, environment variable instructions list Windows first, and .NET/PowerShell are highlighted as management SDKs. While Linux and macOS instructions are present, Windows tools and patterns are often mentioned first or more prominently.
Recommendations
- Provide equal prominence to Linux and macOS instructions by rotating or randomizing the order of OS tabs, or by listing Linux/macOS first in some sections.
- When linking to installation instructions (e.g., Azure CLI), use a cross-platform link or provide links for all major OSes.
- Include more examples using Bash or other common Linux shells, not just PowerShell or Windows command prompt.
- Mention cross-platform SDKs and tools (like Azure CLI and REST APIs) before platform-specific ones (like .NET or PowerShell).
- Ensure that screenshots and sample file paths are not Windows-specific unless necessary.
- Where possible, provide parity in troubleshooting tips and notes for Linux/macOS users.