Communication Services
2083
Total Pages
1869
Linux-Friendly Pages
214
Pages with Bias
10.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
367 issues found
Showing 226-250 of 367 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/teams-interopability/teams-interopability-android.md
...s/teams-interopability/teams-interopability-android.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation includes a direct reference to a Windows-specific SDK installation guide and does not mention Linux or provide Linux-specific installation instructions or examples. The '[!INCLUDE [Install SDK](../install-sdk/install-sdk-windows.md)]' directive points only to Windows, indicating Windows-first bias and missing Linux parity.
Recommendations
- Provide parallel Linux installation instructions or an SDK installation guide for Linux, and include it alongside or before the Windows instructions.
- If cross-platform SDKs are supported, clarify this in the documentation introduction and link to both Windows and Linux installation guides.
- Add Linux-specific usage notes or troubleshooting tips if there are platform differences.
- Ensure that code examples and setup instructions are not platform-specific or, if they are, provide equivalent Linux examples.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/calling-sdk/includes/teams-interopability/teams-interopability-ios.md
...ludes/teams-interopability/teams-interopability-ios.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page includes an 'Install SDK' section that links specifically to a Windows installation guide, with no mention of Linux or cross-platform alternatives. There are no Linux-specific instructions or examples, and the initial setup appears to assume a Windows environment.
Recommendations
- Provide equivalent SDK installation instructions for Linux and macOS, or link to a cross-platform installation guide.
- Explicitly mention platform compatibility and requirements for the SDK and APIs.
- Include Linux/macOS-specific examples or notes where relevant, especially for environment setup and permissions.
- Ensure that referenced guides (such as 'install-sdk-windows.md') have parallel documentation for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/chat-sdk/archive-chat-threads.md
...tion-services/how-tos/chat-sdk/archive-chat-threads.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by linking to chat message listing instructions with a 'tabs=windows' parameter, suggesting Windows is the default or primary platform. There are no explicit Linux or cross-platform examples, and no mention of Linux-specific tools or commands. The documentation does not provide parity for Linux users, nor does it clarify if the instructions are cross-platform.
Recommendations
- Provide explicit Linux and macOS examples or clarify that the instructions are cross-platform.
- Use neutral or platform-agnostic links and code snippets, or include tabs for Windows, Linux, and macOS where relevant.
- Mention and demonstrate use of cross-platform tools (e.g., Azure CLI, REST API) instead of assuming a Windows environment.
- Review all links and references to ensure they do not default to Windows-specific instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/event-grid/view-events-request-bin.md
...services/how-tos/event-grid/view-events-request-bin.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by linking to Azure CLI installation instructions specifically for Windows in both the pre-requisites and configuration steps, without mentioning or providing equivalent instructions for Linux or macOS. There are no examples or guidance for Linux users, and the CLI installation link defaults to Windows, suggesting a Windows-first approach.
Recommendations
- Include installation instructions for Azure CLI on Linux and macOS, or link to the cross-platform installation guide.
- Explicitly mention that Azure CLI is cross-platform and provide guidance for users on different operating systems.
- Add notes or examples for common Linux shell environments (e.g., bash, zsh) where relevant.
- Ensure screenshots and step-by-step instructions are not Windows-centric, or provide alternatives for other platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/router-sdk/azure-function.md
...nication-services/how-tos/router-sdk/azure-function.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation does not explicitly show Windows-specific tools or commands, but it implicitly exhibits Windows bias by only providing C# code examples (commonly associated with Windows development) and not offering equivalent examples in languages or tools more familiar to Linux users (such as Python, JavaScript, or Bash). There are no references to Linux-specific workflows, and the instructions for inspecting the deployed function mention the Azure portal without mentioning CLI alternatives, which may be more common among Linux users.
Recommendations
- Provide code examples in additional languages commonly used on Linux, such as Python or JavaScript, alongside C#.
- Include instructions for inspecting and managing Azure Functions using the Azure CLI or Azure Functions Core Tools, not just the Azure portal.
- Explicitly mention that Azure Functions can be developed and deployed from Linux environments and provide links or notes about cross-platform development.
- Where possible, show terminal/command-line examples for configuration steps, not just SDK or portal-based instructions.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-javascript.md
...ssaging/whatsapp/includes/common-setting-javascript.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides only Windows-specific commands (setx) for setting environment variables, with no equivalent Linux/macOS examples. Windows tools and workflows (Visual Studio, setx) are mentioned exclusively or before any cross-platform alternatives. There is no guidance for Linux or macOS users on setting environment variables, which may hinder non-Windows developers.
Recommendations
- Add Linux/macOS equivalents for setting environment variables, e.g., 'export VAR=value' for Bash/zsh.
- Include cross-platform instructions or a table showing commands for Windows (cmd/PowerShell), Linux, and macOS.
- Mention non-Windows editors (e.g., VS Code) alongside Visual Studio when discussing restarting IDEs.
- Review referenced links to ensure Linux/macOS instructions are present and clearly indicated.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-net.md
...nced-messaging/whatsapp/includes/common-setting-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only C# code examples and references to the Azure portal, with no mention of Linux-specific tools, CLI commands, or cross-platform alternatives. There are no Linux shell or cross-platform code samples, and the workflow assumes use of the Azure portal, which is platform-agnostic but often more familiar to Windows users. No PowerShell-specific commands are present, but the lack of Linux or bash equivalents and the exclusive use of C# (commonly associated with Windows development) indicate a Windows-first and missing Linux example bias.
Recommendations
- Add code examples in additional languages commonly used on Linux, such as Python or JavaScript, especially for command-line or scripting tasks.
- Provide CLI (e.g., Azure CLI) or bash shell command examples for authentication and resource management, alongside or instead of portal instructions.
- Explicitly mention that the SDK and instructions are cross-platform, and provide guidance for Linux/macOS users where workflows may differ.
- Include screenshots or instructions for accessing resources from non-Windows environments if there are differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/interactive/messages-quickstart-interactive-messages-net.md
...active/messages-quickstart-interactive-messages-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Visual Studio (a Windows-centric IDE) first in both the prerequisites and code execution instructions. The 'Run the code' section provides detailed steps for Visual Studio (Windows) before mentioning the .NET CLI, but does not provide any Linux-specific instructions or examples (e.g., using VS Code on Linux, or running .NET CLI commands in a Linux shell). There are no references to Linux tools, shell commands, or Linux-specific environment setup.
Recommendations
- Add explicit instructions for running the code on Linux, such as using the .NET CLI in a Bash shell.
- Include VS Code as a cross-platform IDE in the 'Run the code' section, with Linux-specific steps.
- Mention installation and setup steps for .NET on Linux (e.g., using apt-get or yum).
- Provide example commands for building and running the code in a Linux terminal.
- Clarify that the .NET CLI instructions apply equally to Windows, Linux, and macOS, and provide sample terminal output for Linux.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/reactions/messages-quickstart-reaction-messages-net.md
...reactions/messages-quickstart-reaction-messages-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Visual Studio (a Windows-centric IDE) first in the 'Run the code' section, providing keyboard shortcuts specific to Windows, and omitting explicit Linux or macOS instructions for running .NET code. There are no examples or guidance for Linux-specific development environments, nor are there instructions for running the sample code on Linux terminals or with Linux-specific tools.
Recommendations
- Add explicit instructions for running the code on Linux and macOS, including terminal commands and any required environment setup.
- Include Linux-friendly IDEs (e.g., JetBrains Rider, MonoDevelop) or mention that Visual Studio Code and .NET CLI are cross-platform.
- Provide keyboard shortcuts for building and running code in Visual Studio Code and .NET CLI on Linux/macOS, or clarify that the commands work across platforms.
- Consider adding a note or section highlighting cross-platform compatibility of the .NET SDK and sample code.
Communication Services
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation shows mild Windows bias by mentioning Visual Studio Code and Visual Studio as the only editors/IDEs for running the code, with Visual Studio (a Windows-specific tool) given a dedicated section. There are no explicit Linux or cross-platform editor instructions, and the instructions for running the code in Visual Studio appear before any mention of running from a generic terminal. However, most command-line examples use Bash syntax and Python, which are cross-platform.
Recommendations
- Add explicit instructions for running the code from a generic terminal (e.g., Bash or CMD) on both Windows and Linux/macOS.
- Include examples or mention of popular Linux/macOS editors (e.g., PyCharm, VS Code on Linux, or simply using the terminal).
- Clarify that Visual Studio Code is cross-platform and provide Linux/macOS installation links.
- If providing a Visual Studio section, also provide a section for running from the command line on Linux/macOS.
- Ensure that any tool or workflow mentioned (such as DevTunnels) is available and supported on Linux/macOS, and provide platform-specific notes if there are differences.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-csharp.md
...tion-services/quickstarts/chat/includes/chat-csharp.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a mild Windows bias by listing Windows tools (cmd, PowerShell) before Bash when suggesting console windows, and by recommending Visual Studio as the only IDE without mentioning cross-platform alternatives. There are no explicit Linux-specific instructions or examples, and the setup steps assume familiarity with Windows-centric development environments.
Recommendations
- When listing console options, alternate the order or explicitly mention Bash/terminal first to balance platform representation.
- Mention Visual Studio Code as a cross-platform alternative to Visual Studio, and provide a link to its download page.
- Add a note clarifying that all dotnet CLI commands work identically on Linux, macOS, and Windows.
- If there are any platform-specific steps (e.g., environment variables, file paths), provide Linux/macOS equivalents.
- Consider including a short section or callout for Linux/macOS users, confirming that the instructions are cross-platform.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/chat/includes/chat-logic-app.md
...n-services/quickstarts/chat/includes/chat-logic-app.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Power Automate and Azure Logic Apps, which are primarily Windows-centric tools. All examples and instructions are given in the context of these graphical workflow tools, with no mention of Linux-native equivalents, CLI, or cross-platform scripting options. There are no Linux-specific instructions, nor any parity examples for Linux users.
Recommendations
- Include equivalent instructions for Linux users, such as using Azure CLI, REST API, or SDKs (Python, Node.js, etc.) to perform the same operations.
- Provide examples for automating Communication Services tasks using cross-platform tools and scripting languages.
- Explicitly mention platform requirements and alternatives for users who do not use Windows or Power Automate.
- Add a section comparing workflow automation options on Linux (e.g., Azure Functions, Logic Apps via REST, etc.) and how to achieve similar results.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-azure-managed-domain-resource-dot-net.md
...cludes/create-azure-managed-domain-resource-dot-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page provides only C#/.NET SDK code examples and references to the Azure portal for resource management. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI or Bash), and the authentication guidance refers to a link that defaults to command-line instructions but does not specify Bash or Linux terminal usage. The SDK and tooling focus is on .NET, which is cross-platform but historically Windows-centric. No PowerShell-specific commands are present, but there is a lack of parity for Linux users who may prefer CLI or Bash scripts.
Recommendations
- Add Azure CLI (az) command examples for all resource management operations alongside the C# SDK examples.
- Explicitly mention that .NET Core SDK and the Azure SDK are cross-platform and provide Bash/Linux terminal equivalents for authentication and environment variable setup.
- Include instructions or links for managing resources using Bash scripts or shell commands, not just the Azure portal.
- Where environment variables are used (e.g., AZURE_SUBSCRIPTION_ID), show both Windows (set) and Linux (export) syntax.
- Clarify that all examples work on Linux, macOS, and Windows, and provide troubleshooting tips for common Linux-specific issues if any.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-az-cli.md
...kstarts/email/includes/create-email-resource-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by linking exclusively to the Windows installation instructions for Azure CLI in the prerequisites, without mentioning or providing links for Linux or macOS. All command-line examples use Azure CLI, which is cross-platform, but there is no explicit guidance or reassurance for Linux/macOS users, nor are there any examples or notes about platform differences.
Recommendations
- Add links to Azure CLI installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Include a note stating that Azure CLI commands work on Windows, Linux, and macOS, and mention any platform-specific considerations if relevant.
- Consider providing example commands or screenshots from a Linux terminal to demonstrate parity.
- Avoid using 'azurepowershell-interactive' as the code block language if the commands are Azure CLI, to prevent confusion with PowerShell (which is Windows-centric). Use 'azurecli' or 'bash' where appropriate.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-email-resource-dot-net.md
...starts/email/includes/create-email-resource-dot-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides C#/.NET examples and references to the Azure portal, without mentioning or providing parity for Linux-specific workflows, tools, or shell environments. There are no examples for Linux command-line tools (e.g., Bash, Azure CLI), and the authentication and environment variable setup steps implicitly assume familiarity with Windows or .NET-centric workflows.
Recommendations
- Add Azure CLI and Bash examples for authentication, resource creation, and management tasks, alongside the C#/.NET SDK examples.
- Explicitly mention that the .NET SDK and Azure CLI are cross-platform and provide instructions for Linux and macOS users where relevant.
- Include examples of setting environment variables in Bash (Linux/macOS) as well as in PowerShell/Command Prompt (Windows).
- Reference Linux-friendly tools and workflows (e.g., using the Azure CLI in a terminal) in parallel with Azure portal and .NET SDK options.
- Ensure that any links to SDK downloads or authentication guides highlight cross-platform compatibility and provide platform-specific instructions if needed.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-az-cli.md
...ail/includes/create-sender-username-resource-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows a Windows bias by linking only to the Windows-specific Azure CLI installation guide and not mentioning Linux or macOS installation options. All command-line examples use the Azure CLI, which is cross-platform, but the installation instructions and links are Windows-first. No Linux-specific instructions or terminal conventions are provided.
Recommendations
- Provide installation instructions or links for Azure CLI on Linux and macOS alongside the Windows link.
- Clarify that the Azure CLI commands work on all supported platforms (Windows, Linux, macOS).
- Use neutral or cross-platform code block labels (e.g., 'bash', 'sh', or 'azurecli') instead of 'azurepowershell-interactive', which may imply PowerShell/Windows bias.
- Add a note or section for Linux/macOS users, including any platform-specific considerations (e.g., use of single vs. double quotes, environment variable syntax).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-sender-username-resource-dot-net.md
...il/includes/create-sender-username-resource-dot-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing C#/.NET examples and referencing environment variable usage without platform-specific guidance. There are no examples or instructions for Linux users (e.g., Bash, CLI commands, or Linux-specific environment variable setting), nor is there mention of cross-platform tooling or parity in workflow. The authentication section references a Microsoft Learn page that defaults to command-line instructions but does not clarify Linux usage.
Recommendations
- Add explicit instructions and code examples for setting environment variables on Linux/macOS (e.g., export AZURE_SUBSCRIPTION_ID=...) alongside Windows methods.
- Include Azure CLI or Bash script examples for authentication and resource management to complement the C#/.NET samples.
- Mention cross-platform compatibility of the .NET SDK and clarify any OS-specific steps or differences.
- Provide links to Linux/macOS-specific documentation for SDK installation and usage.
- Where possible, show parity in tooling (e.g., PowerShell vs Bash/CLI) and avoid assuming a Windows-first workflow.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/send-email-python.md
...rvices/quickstarts/email/includes/send-email-python.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by providing only Windows-style commands for activating the Python virtual environment (e.g., '.\Scripts\activate') and omitting the equivalent Linux/macOS commands (e.g., 'source ./bin/activate'). No explicit Linux or macOS instructions or examples are provided for environment setup, which may confuse or hinder non-Windows users.
Recommendations
- Add Linux/macOS equivalents for all terminal commands, especially for virtual environment activation (e.g., 'source ./bin/activate' for bash/zsh).
- Wherever a command is platform-specific, use tabbed sections or callouts to show both Windows and Linux/macOS instructions.
- Explicitly mention that the instructions apply to all platforms, and clarify any platform-specific differences.
- Review the documentation for other subtle Windows-centric assumptions (e.g., path separators, command syntax) and address them for cross-platform clarity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-java.md
...email/send-email-advanced/includes/attachments-java.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a code example that uses a Windows-style file path ('C:/attachment.txt') without mentioning or showing a Linux/macOS equivalent. There are no examples or notes for Linux users, which may cause confusion or extra effort for those on non-Windows platforms.
Recommendations
- Include a Linux/macOS file path example (e.g., '/home/user/attachment.txt') alongside the Windows example.
- Add a note clarifying that file paths are platform-specific and users should adjust them accordingly.
- Consider providing a cross-platform code snippet or guidance on detecting the operating system and setting file paths appropriately.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/email-object-model-net.md
...send-email-advanced/includes/email-object-model-net.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only .NET/C# code examples, which are most commonly used on Windows platforms. There is no mention of Linux-compatible SDKs, alternative programming languages, or cross-platform usage considerations. Console.WriteLine and .NET SDK references implicitly prioritize Windows development environments.
Recommendations
- Include examples using cross-platform languages or frameworks (e.g., Python, Java, Node.js) that are commonly used on Linux.
- Explicitly mention that the .NET SDK is cross-platform and can be used on Linux and macOS, with instructions or links for Linux setup.
- Provide sample commands or troubleshooting steps for Linux environments (e.g., using Bash, Linux terminal).
- Reference Linux email clients or tools alongside Outlook when discussing header recognition.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/attachments-net.md
.../email/send-email-advanced/includes/attachments-net.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a file path example using Windows-style paths (e.g., C:\Users\Documents\attachment.pdf) and does not mention or provide examples for Linux or macOS file paths. There are no Linux-specific instructions or notes, and the only example given could confuse or exclude Linux users.
Recommendations
- Include Linux/macOS file path examples (e.g., /home/user/attachment.pdf) alongside the Windows example.
- Add a note clarifying that file paths should be adapted to the user's operating system.
- Ensure that code samples and instructions are cross-platform or provide OS-specific variants where necessary.
- Explicitly mention that the .NET SDK and dotnet CLI are cross-platform and can be used on Linux/macOS as well as Windows.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp-oauth.md
...kstarts/email/send-email-smtp/send-email-smtp-oauth.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by listing Windows-specific consoles (cmd, PowerShell) before Bash when describing where to run commands. There are no Linux-specific instructions, troubleshooting tips, or examples, and the guidance assumes parity without verifying Linux-specific nuances (e.g., package installation, environment setup).
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and instructions.
- Provide Linux/macOS-specific instructions for installing .NET Core and MailKit, including package manager commands (e.g., apt, yum, brew).
- List Bash first or equally alongside Windows consoles when referencing command-line usage.
- Add troubleshooting notes for common Linux issues (e.g., permissions, firewall, OpenSSL dependencies).
- Include screenshots or terminal output examples from Linux environments.
- Clarify any platform-specific differences in SMTP connectivity or authentication.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-az-cli.md
...ts/events/includes/create-event-subscription-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by linking to the Windows-specific Azure CLI installation guide in the prerequisites, without mentioning or linking to Linux or macOS installation instructions. All command-line examples use the cross-platform Azure CLI, which is good, but there are no explicit Linux or macOS installation or usage examples, nor is there mention of platform-specific considerations.
Recommendations
- Update the Azure CLI installation link to point to the general installation page or include links for Windows, Linux, and macOS.
- Explicitly mention that the Azure CLI commands work on all supported platforms (Windows, Linux, macOS).
- Optionally, provide a short note or example showing command execution in a Linux/macOS shell, or clarify that the examples are platform-agnostic.
- Avoid defaulting to Windows-specific links or instructions in cross-platform documentation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/register-event-grid-resource-provider.md
...ents/includes/register-event-grid-resource-provider.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes how to register the Event Grid resource provider using the Azure portal (a GUI tool), which is most commonly used on Windows. There are no examples or instructions for performing the same task using cross-platform tools such as the Azure CLI or Azure PowerShell, which are commonly used on Linux and macOS. This omission results in a bias towards Windows users.
Recommendations
- Add instructions for registering the Event Grid resource provider using the Azure CLI, which works on Linux, macOS, and Windows.
- Include Azure PowerShell examples, clarifying that PowerShell Core is cross-platform.
- Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide command-line alternatives for automation and parity.
- Ensure that future documentation sections provide both GUI and CLI-based instructions to support all platforms equally.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/access-tokens/access-token-az-cli.md
...identity/includes/access-tokens/access-token-az-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation exhibits a Windows-first bias in several areas. Installation instructions for the Azure CLI link directly to the Windows-specific page, and in environment variable setup sections, Windows instructions are consistently presented before macOS and Linux. The use of Windows-specific tools (e.g., setx) is highlighted, and Visual Studio is referenced as the default editor example, reinforcing a Windows-centric perspective. However, Linux and macOS instructions are present and technically complete.
Recommendations
- Provide a cross-platform Azure CLI installation link or mention all OS options equally, rather than linking only to the Windows installer.
- Rotate or randomize the order of OS tabs (Windows, macOS, Linux) or default to a neutral/cross-platform tab to avoid always presenting Windows first.
- When referencing editors or IDEs, include popular cross-platform or Linux editors (e.g., VS Code, JetBrains IDEs, Vim) alongside Visual Studio.
- Ensure that all command-line examples and environment variable instructions are equally detailed and visible for Linux and macOS, not just Windows.
- Consider adding a short note at the start of environment variable sections stating that instructions are available for all major OSes, to reinforce parity.