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 51-75 of 367 flagged pages
Communication Services
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
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Teams PowerShell and Microsoft Teams Client (both Windows-centric tools) as the primary methods for assigning delegates. No Linux or cross-platform alternatives are mentioned, and the examples/tools listed are Windows-specific. The SDK support table lists 'Windows' as a platform but does not mention Linux or macOS, and there are no Linux-specific instructions or parity.
Recommendations
- Include Linux and macOS alternatives for assigning delegates, such as web-based or REST API methods if available.
- Explicitly mention cross-platform compatibility for SDKs and tools, and add Linux/macOS columns to the support table.
- Provide command-line examples using bash or other Linux-native tools where possible.
- Clarify whether Teams PowerShell or Teams Client functionality is available via browser or on non-Windows platforms, and link to relevant documentation.
- Add a section addressing platform support and limitations, including any Linux-specific guidance or caveats.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/how-tos/managed-identity.md
...les/communication-services/how-tos/managed-identity.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing the Azure Portal (a GUI tool most commonly used on Windows) and Azure CLI examples, with CLI code blocks labeled as 'azurepowershell-interactive' and 'azurecli-interactive'. There is no mention of Linux-specific shell environments, nor are there explicit Bash or cross-platform shell examples. The documentation does not provide any Linux-specific instructions or screenshots, and the use of the Azure Portal is presented first in all cases.
Recommendations
- Add explicit Bash/Linux shell examples for all CLI commands, using the 'bash' code block label where appropriate.
- Clarify that the Azure CLI commands work cross-platform (Windows, macOS, Linux) and provide any necessary notes about differences in shell syntax.
- Include screenshots or instructions for the Azure Portal on Linux/macOS (if available), or clarify platform requirements.
- Avoid labeling CLI code blocks as 'azurepowershell-interactive' unless they are specifically for PowerShell; use 'azurecli' or 'bash' as appropriate.
- Consider providing a 'Linux/macOS' tab for steps that might differ from Windows, especially for command-line usage.
- Explicitly mention that all SDKs and CLI commands are supported on Linux, and provide links to Linux installation guides for Azure CLI if not already present.
Communication Services
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 demonstrates Windows bias by exclusively referencing the Windows 'nslookup' command for DNS verification, linking to Windows Server documentation, and not mentioning or providing equivalent Linux/macOS commands (such as 'dig' or 'nslookup' on Linux). No Linux or cross-platform examples are given, and the Windows tool is presented as the default/only method.
Recommendations
- Include Linux/macOS equivalents for DNS verification, such as 'dig -t txt subdomain.contoso.com' or 'nslookup -type=txt subdomain.contoso.com' (noting that 'nslookup' is also available on Linux).
- Provide links to cross-platform or Linux/macOS documentation for DNS tools, not just Windows Server documentation.
- Use neutral language such as 'You can use DNS query tools (e.g., nslookup or dig) on your platform to verify...' rather than only referencing Windows tools.
- Consider providing example commands for both Windows and Linux/macOS environments side by side.
Communication Services
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
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation consistently uses the Windows-specific 'setx' command for setting environment variables, without providing equivalent commands for Linux or macOS (e.g., 'export' for bash/zsh). All environment variable instructions and examples are Windows-centric, and there is no mention of Linux or cross-platform alternatives. Additionally, references to restarting Visual Studio reinforce a Windows development environment bias.
Recommendations
- For every environment variable example using 'setx', provide equivalent Linux/macOS commands (e.g., 'export VAR=value' for bash/zsh, or instructions for adding to ~/.bashrc or ~/.zshrc).
- Explicitly mention that the instructions apply to Windows, and provide parallel instructions for Linux/macOS users.
- Include notes or tabs for different operating systems, so users can select their platform and see relevant commands.
- When referencing tools like Visual Studio, also mention cross-platform editors (e.g., VS Code) and clarify any platform-specific steps.
- Link to official Microsoft documentation on setting environment variables for all supported operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/common-setting-java.md
...ced-messaging/whatsapp/includes/common-setting-java.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by providing only Windows-specific commands (setx) for setting environment variables, and referencing Windows tools (Visual Studio) without mentioning Linux or macOS equivalents. There are no examples or instructions for Linux or macOS users, such as using export or setting environment variables in bash/zsh shells.
Recommendations
- Add Linux/macOS equivalents for setting environment variables (e.g., export VAR=value for bash/zsh).
- Include instructions or notes for users of common Linux/macOS shells (bash, zsh, etc.).
- When referencing Windows tools (e.g., Visual Studio), also mention popular Linux/macOS editors (e.g., VS Code, JetBrains IDEs) and note any platform-specific steps.
- Present cross-platform instructions together, or use tabs to separate Windows, Linux, and macOS steps.
- Review all command-line examples to ensure parity across platforms.
Communication Services
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
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows development tools (Visual Studio, Visual Studio Code) and .NET CLI, with all code examples in C#. There are no explicit Linux or cross-platform instructions, and no mention of Linux-specific development environments or commands. The guidance for building and running the code is focused on Windows-centric tools and workflows, with no Linux or macOS parity.
Recommendations
- Add explicit instructions for building and running the code on Linux and macOS, including terminal commands and any required dependencies.
- Mention and provide examples for using cross-platform editors (e.g., VS Code on Linux/macOS) and the .NET CLI on non-Windows systems.
- Include a section on installing .NET SDK on Linux and macOS, with links to official documentation.
- Clarify that the .NET CLI and Visual Studio Code are cross-platform, and provide parity in instructions for all supported operating systems.
- Consider providing code examples in additional languages (such as Python or JavaScript) if the SDK supports them, or clarify that only .NET is supported.
Communication Services
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') to create a new file, without offering the equivalent Linux/macOS command (e.g., 'touch messages-quickstart.py'). All other instructions are platform-neutral, but the file creation step demonstrates a Windows bias by only mentioning a Windows tool and not providing parity for Linux users.
Recommendations
- Provide both Windows and Linux/macOS commands for creating new files. For example, show 'type nul > messages-quickstart.py' for Windows and 'touch messages-quickstart.py' for Linux/macOS.
- Consider using platform-neutral language or call out platform-specific steps explicitly.
- Review the documentation for other steps that may assume a particular OS and ensure parity for Linux users.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/stickers/messages-quickstart-sticker-messages-net.md
...s/stickers/messages-quickstart-sticker-messages-net.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 prioritizing Windows-centric tools and workflows. Visual Studio (a Windows-first IDE) is mentioned before Visual Studio Code and .NET CLI, and keyboard shortcuts are given for Visual Studio only (which are Windows-specific). There are no explicit Linux or macOS instructions, nor are there any terminal or shell examples for Linux users. The documentation assumes familiarity with Windows development environments and omits guidance for Linux users.
Recommendations
- Add explicit instructions and examples for Linux users, such as using the .NET CLI in Bash or other Linux shells.
- Mention cross-platform editors (e.g., Visual Studio Code) and the .NET CLI before or alongside Visual Studio.
- Include Linux/macOS-specific build and run instructions, including relevant keyboard shortcuts or terminal commands.
- Clarify that the .NET SDK and CLI are cross-platform and provide links to installation guides for Linux/macOS.
- Avoid assuming the use of Windows-only tools or workflows; ensure parity in documentation for all supported platforms.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md
...kstart-make-an-outbound-call-using-callautomation-node.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias by recommending Visual Studio Code (which, while cross-platform, is often associated with Windows) and Azure DevTunnels (whose CLI and setup instructions are more familiar to Windows users). There are no explicit Linux-specific instructions, troubleshooting tips, or alternative tools mentioned. All command-line examples are generic, but there is an implicit assumption of a Windows-like environment (e.g., use of .env files, Visual Studio Code, and lack of mention of Linux shells or editors).
Recommendations
- Explicitly state that all commands work on Linux, macOS, and Windows, or provide OS-specific notes where differences exist.
- Include Linux-specific setup instructions or troubleshooting tips, such as using alternative editors (e.g., Vim, Nano) or confirming that Azure DevTunnels CLI is available and works on Linux.
- Mention that Visual Studio Code is cross-platform, and suggest alternatives for users who prefer other editors.
- Add a note about how to set environment variables in Linux/macOS shells if manual export is needed.
- If there are any Windows-specific behaviors (such as path formats or CLI differences), document the Linux equivalents.
Communication Services
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 demonstrates a moderate Windows bias. Windows-specific tools and instructions (such as PowerShell and setx) are presented first or exclusively in several sections. The Azure CLI installation link defaults to Windows, and PowerShell is given its own pivot, while Linux and macOS are grouped under 'unix' or 'linux' tabs. Windows environment variable instructions are presented before Linux/macOS. There is a lack of parity in the prominence and detail of Linux examples and tools.
Recommendations
- Present Linux/macOS instructions and tools with equal prominence to Windows, including placing them before or alongside Windows examples rather than after.
- Provide direct links to Azure CLI installation instructions for Linux and macOS, not just Windows.
- Ensure that all PowerShell examples have Bash equivalents, and consider providing Bash as a primary example where possible.
- Use neutral language and ordering in tabbed instructions (e.g., Linux/macOS first or randomized order).
- Add explicit mention and examples for Linux-native tools and patterns where relevant, not just as an afterthought.
Communication Services
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its DNS record instructions, which link to guides for adding DNS records using Windows-based DNS tools, but do not provide explicit Linux or cross-platform alternatives. The 'Other (General)' CNAME record link specifically points to a Windows-based DNS guide, and there are no references to Linux command-line tools (e.g., dig, nsupdate, bind) or Linux DNS server management. The platform pivots include Azure CLI (cross-platform), .NET, and PowerShell (Windows-centric), but there is no explicit Linux shell or tool example, nor is Linux mentioned in the DNS record management section.
Recommendations
- Add explicit instructions or links for managing DNS records using Linux tools (e.g., bind, nsupdate, editing /etc/bind/named.conf, using dig for verification).
- Provide parity by including Linux shell examples alongside PowerShell, especially for Azure resource management and DNS configuration.
- Replace or supplement the 'Other (General)' CNAME record link with a cross-platform or Linux-specific guide, rather than only referencing Windows-based DNS.
- Clarify in each section which instructions are platform-agnostic and which are Windows-specific, and offer alternatives where possible.
- Consider adding a Linux-focused pivot (e.g., Bash, Linux shell) for resource provisioning and configuration steps.
Communication Services
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 exhibits a Windows-first bias by linking only to the Windows Azure CLI installation instructions and using the 'azurepowershell-interactive' code block type for all CLI examples. There are no explicit Linux or macOS installation links, nor are there any shell-specific (bash/zsh) examples or notes about cross-platform usage. This may give the impression that the instructions are primarily for Windows users.
Recommendations
- Provide installation links for Azure CLI on Linux and macOS alongside the Windows link.
- Use neutral code block types (e.g., 'bash' or 'sh') for CLI commands instead of 'azurepowershell-interactive', since the Azure CLI is cross-platform.
- Add a note clarifying that all Azure CLI commands work on Windows, Linux, and macOS terminals.
- Include example commands or screenshots from a Linux shell to demonstrate parity.
- Avoid using terminology or code block types that imply a Windows-only environment when the tool is cross-platform.
Communication Services
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
Windows First
Summary
The documentation exclusively uses PowerShell commands and the Azure Az PowerShell module for all examples and instructions. There are no examples or instructions for Linux users (e.g., using Azure CLI or Bash). Windows tools and patterns are mentioned exclusively and are presented as the default/only option, which may alienate or confuse Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI (az) command examples for all operations (e.g., creating, updating, listing, and deleting Domain resources).
- Mention that PowerShell can be used cross-platform, but clarify installation steps for Linux/macOS if PowerShell is required.
- Add a section or callout for Linux/macOS users, explaining their options and linking to relevant Azure CLI or REST API documentation.
- Avoid presenting Windows/PowerShell tools as the only or default method; strive for parity by listing cross-platform tools first or side-by-side.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/includes/create-custom-managed-domain-resource-az-cli.md
...cludes/create-custom-managed-domain-resource-az-cli.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation consistently uses 'azurepowershell-interactive' code blocks for all CLI examples, which implies a Windows/PowerShell environment. The Azure CLI installation link points to the Windows-specific instructions by default, and there is no mention of Linux or macOS equivalents. No Bash or cross-platform shell examples are provided, and there is no guidance for Linux users.
Recommendations
- Provide Bash or generic shell examples for all Azure CLI commands, using 'bash' or 'sh' code blocks instead of 'azurepowershell-interactive'.
- Update the Azure CLI installation link to either a cross-platform landing page or include links for Linux and macOS installation instructions.
- Explicitly state that the Azure CLI commands work on all platforms (Windows, Linux, macOS) and clarify any platform-specific steps if needed.
- Avoid using PowerShell-specific syntax or code block types unless there is a platform-specific reason.
- Add a section or callout for Linux/macOS users to ensure parity and inclusivity.
Communication Services
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 operations, without providing any examples or guidance for Linux users or cross-platform alternatives such as Azure CLI, Bash, or REST API. This creates a strong Windows/PowerShell bias, making it less accessible for users on Linux or macOS.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the Azure Az PowerShell Module is available on all platforms, or clarify any platform-specific requirements.
- Include Bash or shell script examples where appropriate, especially for common tasks like authentication and resource management.
- Reference REST API documentation or provide REST examples for advanced users who may prefer direct API calls.
- Reorganize the documentation to present cross-platform or CLI options before or alongside PowerShell examples, to avoid the impression of Windows-first bias.
Communication Services
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 references Windows-centric tools (Azure Az PowerShell), with no mention of Linux or cross-platform alternatives such as Azure CLI, Bash, or shell scripts. All examples and instructions assume a Windows environment, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add equivalent Azure CLI examples for all resource management tasks (creating, updating, listing, and deleting Email Communication Service resources).
- Explicitly mention cross-platform compatibility and provide instructions for Linux and macOS users.
- Reference installation guides for Azure CLI and Bash usage alongside PowerShell.
- Reorder sections or provide parallel examples so that Linux/macOS instructions are presented with equal prominence as Windows/PowerShell instructions.
- Clarify which commands are platform-specific and suggest alternatives where appropriate.
Communication Services
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 (Az PowerShell Module) for all examples and instructions, which are Windows-centric. There are no examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
- Add 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 must be used, and provide instructions for installing and using it on Linux/macOS.
- Include Bash shell examples where appropriate, especially for common tasks.
- Provide a section or note for Linux/macOS users, outlining supported tools and any differences in usage.
- Ensure that links to documentation for Azure CLI and other cross-platform tools are included alongside PowerShell links.
Communication Services
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
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns first (e.g., cmd, PowerShell), omitting explicit Linux/macOS shell examples, and not addressing cross-platform differences in environment variable setup or command-line usage. All code and instructions are C#/.NET-centric, which is cross-platform, but the examples and terminal references default to Windows environments.
Recommendations
- Explicitly mention and provide examples for Linux/macOS terminals (e.g., Bash, zsh) alongside Windows (cmd/PowerShell) in all command-line instructions.
- Show how to set environment variables in both Windows (setx/PowerShell) and Linux/macOS (export in Bash/zsh).
- When referencing 'console window', use inclusive language such as 'terminal (cmd, PowerShell, or Bash)' and alternate the order in which platforms are mentioned.
- Add a note clarifying that all .NET commands work on Linux/macOS as well, and provide troubleshooting tips for common cross-platform issues.
- Where file paths or editor usage is mentioned, provide examples for both Windows and Linux/macOS (e.g., using nano/vim vs. notepad).
Communication Services
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 focused on Windows and PowerShell, with all examples and setup instructions using Azure PowerShell and Windows-specific commands. There are no Linux or cross-platform CLI examples, and the prerequisite steps explicitly mention Windows PowerShell. No mention is made of Bash, Azure CLI, or other Linux-compatible tools, which may exclude or confuse Linux users.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Include Bash shell examples for Linux users, especially for tasks like reading files and constructing email payloads.
- Update the prerequisites to mention both PowerShell and Azure CLI, and clarify which steps are platform-specific.
- Provide guidance for installing and using Azure Communication Services modules/tools on Linux and macOS.
- Ensure that all code samples are available in both PowerShell and Bash/Azure CLI formats, or clearly indicate platform compatibility.
Communication Services
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 is heavily focused on .NET and C# with all code examples and instructions tailored to the .NET SDK. Command-line instructions reference 'cmd', 'PowerShell', and 'Bash' equally, but the overall workflow assumes a Windows-centric development environment (e.g., Visual Studio, .NET, C#). There are no Linux-specific examples, troubleshooting steps, or alternative SDKs (such as Python, Java, or Node.js) shown. The use of .NET as the only SDK and C# as the only language, along with references to Windows command prompts first, demonstrates a Windows bias.
Recommendations
- Add equivalent examples using other supported SDKs (e.g., Python, Java, JavaScript) and show how to run them on Linux.
- Include explicit Linux/macOS shell commands (e.g., bash/zsh) and troubleshooting tips for common Linux environments.
- When mentioning command-line interfaces, list 'Bash' or 'Terminal' before 'cmd' and 'PowerShell', or present them in parallel.
- Provide links or references to cross-platform development tools and editors (e.g., VS Code) rather than assuming Visual Studio or Windows.
- Add a section or callout for Linux users, including any OS-specific prerequisites or package installation instructions.
Communication Services
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 focused on Windows and PowerShell, with all examples and instructions using Azure PowerShell commands and Windows-specific patterns. There are no Linux or cross-platform CLI examples, and the prerequisite explicitly references Windows PowerShell. Linux users are not provided with equivalent instructions or code samples, which may hinder their ability to follow the guide.
Recommendations
- Add equivalent instructions and code samples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
- Explicitly mention support for Linux and macOS environments in the prerequisites and setup sections.
- Provide bash or shell script examples for common tasks, such as sending emails and handling attachments.
- Clarify whether the Az.Communication module can be used in PowerShell Core on Linux/macOS, and provide installation guidance if so.
- If PowerShell is required, include instructions for installing and running PowerShell Core on Linux/macOS, and test all examples for compatibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/inline-attachments-azcli.md
...nd-email-advanced/includes/inline-attachments-azcli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, particularly in the installation instructions for Azure CLI, which link directly to the Windows installer. The environment variable setup section lists Windows instructions first, and the Linux/macOS instructions are less detailed and somewhat generic. There are no Linux-specific troubleshooting tips or examples, and the documentation does not mention Linux-specific shell or editor considerations beyond a brief note about .bash_profile and .zshrc.
Recommendations
- Provide direct links to Azure CLI installation instructions for Linux and macOS alongside the Windows link in the prerequisites.
- Present environment variable setup instructions in a neutral order (e.g., tabs for Windows, macOS, Linux in alphabetical order or with Linux first, or no implied priority).
- Include Linux-specific troubleshooting tips, such as common permission issues or shell differences.
- Mention common Linux editors (e.g., nano, vim) for editing profile files, not just the file names.
- Ensure all examples and instructions are equally detailed for Linux, macOS, and Windows, including any OS-specific caveats.
- Consider adding a note that the Azure CLI commands work identically across platforms, and highlight any differences if they exist.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/send-email-with-inline-attachments.md
...d-email-advanced/send-email-with-inline-attachments.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides language pivots for multiple SDKs, but includes a dedicated PowerShell section without an equivalent for Bash or Linux shell scripting. PowerShell (a Windows-centric tool) is given equal prominence to cross-platform SDKs, and there is no mention or example of using Bash, curl, or other Linux-native tools for scripting email sending. This may make Linux users feel less supported.
Recommendations
- Add a Bash or shell scripting example for sending emails with inline attachments, using tools like curl or the Azure CLI.
- If PowerShell is included, ensure that a comparable Bash/Linux shell example is also present and given equal prominence.
- Clarify in the documentation which examples are cross-platform and which are Windows-specific.
- Consider adding a note about PowerShell Core's cross-platform support if relevant, or otherwise direct Linux users to alternative methods.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-advanced/includes/prepend-net.md
...arts/email/send-email-advanced/includes/prepend-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows command-line tools (cmd, PowerShell) before Bash, and by not providing any Linux-specific examples or guidance. All command-line instructions are given in a generic form but reference Windows environments first. There are no Linux- or macOS-specific installation, environment variable, or troubleshooting instructions.
Recommendations
- Present Bash (Linux/macOS) examples before or alongside Windows (cmd/PowerShell) examples, especially for command-line instructions.
- Explicitly mention Linux/macOS compatibility in the prerequisites and provide platform-specific installation or troubleshooting notes where relevant.
- Include example commands for setting environment variables on Linux/macOS (e.g., export COMMUNICATION_SERVICES_CONNECTION_STRING=...) in addition to Windows (set ...).
- Where file paths or editors are referenced, provide cross-platform alternatives (e.g., nano, vim, or Visual Studio Code for Linux/macOS).
- Add a section or callout for common Linux/macOS issues or differences, such as .NET SDK installation steps for those platforms.
Communication Services
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 code examples using PowerShell and the Send-MailMessage cmdlet, which are native to Windows. There are no examples or guidance for sending email via SMTP from Linux or macOS environments, nor are cross-platform tools (such as sendmail, mailx, or Python scripts) mentioned. This creates a strong Windows bias and may exclude or confuse users on non-Windows platforms.
Recommendations
- Add equivalent instructions and code examples for Linux and macOS environments, using common tools such as sendmail, mailx, or Python's smtplib.
- Explicitly mention cross-platform alternatives and provide links to relevant documentation.
- Structure the documentation to present cross-platform or Linux/macOS examples alongside or before Windows/PowerShell examples.
- Clarify any platform-specific requirements or limitations for the SMTP process.