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 76-100 of 367 flagged pages
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/includes/send-email-smtp-smtpclient.md
...send-email-smtp/includes/send-email-smtp-smtpclient.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (cmd, PowerShell) before cross-platform options (Bash), and does not provide any Linux- or macOS-specific instructions or examples. All code and terminal instructions are generic, but the explicit mention of Windows tools first and lack of Linux-specific troubleshooting or environment notes suggests a bias toward Windows users.
Recommendations
- List Bash (Linux/macOS) before or alongside cmd and PowerShell when mentioning console windows.
- Explicitly state that the .NET Core SDK and all commands work on Linux and macOS, not just Windows.
- Provide Linux/macOS-specific notes, such as how to install .NET Core on those platforms, or how to run the commands in a typical Linux terminal.
- Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, SSL/TLS, firewall).
- Ensure that all instructions and examples are clearly marked as cross-platform, or provide platform-specific sections if behavior differs.
Create Pull Request
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/send-email-smtp.md
...s/quickstarts/email/send-email-smtp/send-email-smtp.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides examples for sending email via SMTP using SmtpClient (typically .NET, often Windows-centric) and Windows PowerShell, but does not include Linux-specific tools or examples (such as sendmail, mailx, or Python scripts on Linux). Windows tools and patterns are mentioned exclusively, and Linux alternatives are missing.
Recommendations
- Add Linux-specific examples for sending email via SMTP, such as using sendmail, mailx, or Python scripts with smtplib.
- Include cross-platform .NET Core examples that run on both Windows and Linux.
- Provide clear instructions for Linux users, including installation and usage of relevant tools.
- Ensure that examples are balanced between Windows and Linux, or explicitly note platform limitations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email-smtp/smtp-authentication.md
...ickstarts/email/send-email-smtp/smtp-authentication.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses the Azure Portal (web UI) for all configuration steps, with screenshots and instructions tailored to the portal interface. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), nor are there any Linux-specific instructions or considerations. The documentation implicitly assumes use of the Azure Portal, which is most commonly accessed from Windows environments, and does not mention or provide parity for Linux users who may prefer CLI tools or automation.
Recommendations
- Add Azure CLI examples for all resource and role assignment steps, including commands for creating service principals, assigning roles, and creating SMTP usernames.
- If PowerShell examples are provided in other documentation, ensure equivalent Bash/Azure CLI examples are present and shown first or side-by-side.
- Mention that all steps can be performed from any OS using the Azure Portal, but highlight CLI alternatives for Linux users.
- Include a section or appendix with Linux/Bash command-line equivalents for common tasks, such as using az commands to manage resources and permissions.
- Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., avoid referencing Windows-specific UI elements or terminology).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/email/send-email.md
...communication-services/quickstarts/email/send-email.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page includes a dedicated section for Azure PowerShell, a Windows-centric tool, and lists it as a top-level platform pivot, potentially before or at parity with Linux-native options. While Azure CLI (cross-platform) is included, there is no explicit mention of Bash or Linux shell scripting, and no Linux-specific troubleshooting or cleanup examples. The presence of PowerShell as a primary method and the lack of Linux-specific examples or tools indicate a mild Windows bias.
Recommendations
- Add explicit Bash or Linux shell examples for sending emails using Azure Communication Services.
- Ensure that Linux-native tools and examples (e.g., Bash scripts, curl, or other CLI utilities) are presented alongside or before PowerShell examples.
- Include troubleshooting and cleanup instructions specific to Linux environments.
- Clearly indicate the cross-platform nature of Azure CLI and provide sample commands in both Windows (PowerShell/CMD) and Linux (Bash) syntax where applicable.
- Review the order of platform pivots to avoid consistently listing Windows tools (like PowerShell) before Linux equivalents.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/events/includes/create-event-subscription-powershell.md
...vents/includes/create-event-subscription-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively uses Azure PowerShell (Windows-centric) for all examples and instructions. There are no examples using Azure CLI, Bash, or other cross-platform tools. The prerequisites and all command-line instructions assume PowerShell, which is most common on Windows, and there is no mention of Linux or macOS alternatives.
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 PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation instructions.
- Include Bash shell examples where appropriate, especially for scripting scenarios.
- In the prerequisites, list both PowerShell and Azure CLI as options, and link to their respective installation guides for different operating systems.
- For each operation (create, list, update, delete), provide both PowerShell and CLI command examples, and clearly label them.
- Avoid assuming the user is on Windows (e.g., do not use 'PS C:\>' prompt exclusively).
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-cli.md
...ity/includes/active-directory/service-principal-cli.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently references Windows-specific resources and examples first or exclusively. All quickstart links for enabling managed identities are for Windows VMs, and there are no Linux VM equivalents or explicit Linux instructions. The guidance for setting environment variables does not mention Linux/macOS shell commands or patterns, and references to Visual Studio reinforce a Windows-centric perspective.
Recommendations
- Include links and examples for enabling managed identities on Linux VMs, not just Windows VMs.
- Provide explicit Linux/macOS shell commands for setting environment variables (e.g., export statements for Bash/Zsh).
- Mention cross-platform development environments (such as VS Code) in addition to or instead of Visual Studio.
- Ensure that all instructions and code samples are clearly marked as cross-platform or provide platform-specific alternatives where necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/manage-teams-identity.md
...nication-services/quickstarts/manage-teams-identity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias, particularly in administrative steps. PowerShell is the only command-line tool referenced for resolving service principal issues, with no mention of Linux or cross-platform alternatives (e.g., Azure CLI, Bash). The instructions for installing modules and running commands assume a Windows/PowerShell environment. No Linux-specific or cross-platform command examples are provided, and Windows tools and patterns are mentioned exclusively and before any Linux equivalents.
Recommendations
- Provide equivalent Azure CLI or Bash commands for all PowerShell instructions, especially for service principal creation and module installation.
- Explicitly mention that PowerShell Core is available cross-platform, or clarify if only Windows PowerShell is supported.
- Add Linux/macOS-specific instructions or notes where administrative actions are required.
- Reorder or parallelize instructions so that cross-platform tools (e.g., Azure CLI) are presented before or alongside Windows/PowerShell tools.
- Include troubleshooting steps for Linux/macOS users, such as how to install required tools and run commands in their environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/identity/microsoft-entra-id-authentication-integration.md
...ntity/microsoft-entra-id-authentication-integration.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. While it does mention the Azure CLI (which is cross-platform), most administrative actions are described in the context of the Azure portal (a web UI, but often associated with Windows environments), and there is a lack of explicit Linux-specific guidance or examples. No Linux shell (bash) or automation examples are provided, and PowerShell is not mentioned, but the absence of Linux-specific instructions or parity in command-line examples suggests a Windows-centric approach. The documentation also refers to the Azure portal and Microsoft Entra admin center without clarifying cross-platform accessibility or alternatives for Linux users.
Recommendations
- Add explicit Linux shell (bash) examples for all CLI commands, especially for service principal creation and resource assignment.
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide installation instructions for Linux users.
- Include screenshots or instructions for using the Azure portal and Microsoft Entra admin center from non-Windows environments (e.g., Linux browsers).
- Mention and provide links to Linux-native tools or automation options where available.
- Ensure that any references to GUI tools (Azure portal, Entra admin center) note their cross-platform nature and accessibility.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/includes/router-quickstart-net.md
...s/quickstarts/router/includes/router-quickstart-net.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-specific consoles (cmd, PowerShell) before Bash, focusing exclusively on .NET and C# (which are cross-platform but have a strong Windows association), and omitting explicit Linux/macOS-specific instructions or examples. No Linux-specific tools, shell commands, or troubleshooting steps are provided, and the only terminal commands shown are generic dotnet CLI commands. There are no references to Linux package managers or environment setup, and the documentation does not mention running the sample on Linux or macOS, nor does it address potential platform-specific issues.
Recommendations
- Explicitly mention Linux and macOS as supported platforms in the prerequisites and setup sections.
- Provide Linux/macOS-specific instructions or notes where relevant (e.g., using Bash, zsh, or different path separators).
- Include example commands for common Linux shells (e.g., Bash, zsh) alongside Windows (cmd, PowerShell) where applicable.
- Reference Linux package managers (such as apt, yum, or snap) for installing .NET, or link to official cross-platform installation guides.
- Add troubleshooting tips for common Linux/macOS issues (such as permissions, environment variables, or path problems).
- Ensure that all screenshots, file paths, and code snippets are platform-agnostic or provide alternatives for different operating systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/router/job-router-azure-openai-integration.md
...ckstarts/router/job-router-azure-openai-integration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Visual Studio Code and its Azure Functions extension, with no mention of Linux-specific alternatives or instructions. All tooling and setup steps assume a Windows environment, and there are no examples or guidance for Linux users (e.g., using the Azure Functions Core Tools CLI, terminal commands, or deployment via Bash). The console application is .NET-based, which is cross-platform, but the documentation does not clarify Linux compatibility or provide Linux-specific instructions.
Recommendations
- Add explicit instructions for Linux users, including how to install and use Visual Studio Code and the Azure Functions extension on Linux.
- Include alternative setup and deployment steps using Azure Functions Core Tools CLI, which works on Linux and macOS.
- Provide terminal/Bash command examples alongside or instead of GUI-based instructions.
- Clarify that the .NET console application can be run on Linux and provide any necessary steps for .NET SDK installation on Linux.
- Mention cross-platform compatibility wherever applicable, and avoid assuming a Windows-only environment.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/receive-sms-no-code.md
...rvices/quickstarts/sms/includes/receive-sms-no-code.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes workflows using Logic Apps and Power Automate, which are primarily Microsoft (Windows-centric) tools. There are no examples or mentions of Linux-native alternatives, command-line tools, or cross-platform automation options. The screenshots and instructions focus solely on the Power Automate UI, with no parity for Linux users or those using open-source automation tools.
Recommendations
- Add examples using Azure CLI, Azure SDKs (e.g., Python, Node.js), or REST API calls to handle Event Grid events and send SMS, which are cross-platform.
- Mention and provide guidance for using open-source or Linux-friendly automation tools (e.g., Apache Airflow, custom scripts) to process events and send SMS.
- Clarify that Logic Apps and Power Automate are not the only options, and link to documentation for alternative approaches suitable for Linux environments.
- Include at least one end-to-end example that can be executed from a Linux shell, such as using bash scripts with curl or az CLI.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/sms/includes/send-sms-java.md
...ion-services/quickstarts/sms/includes/send-sms-java.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides explicit examples for Command Prompt and PowerShell (both Windows environments) when running Maven commands, but does not include any examples for Linux or macOS shells (such as Bash or Zsh). This may make it less accessible for users on non-Windows platforms, as they are left to infer the correct syntax for their environment.
Recommendations
- Add explicit Bash (or generic Unix shell) command examples alongside Command Prompt and PowerShell, especially for Maven commands.
- When listing command-line instructions, present Bash/Linux examples first or at least equally with Windows examples.
- Include a note clarifying that the Maven commands can be run in any terminal, and provide the syntax differences (if any) for Linux/macOS users.
- Review the documentation for any other places where Windows tools or patterns are assumed, and ensure Linux parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/phone-numbers-net.md
...es/quickstarts/telephony/includes/phone-numbers-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by mentioning Windows-specific shells (cmd, PowerShell) before Bash, and by not providing explicit Linux or macOS-specific instructions or examples. All command-line examples use .NET CLI commands, which are cross-platform, but there is no confirmation or illustration of these commands being run in a Linux environment (e.g., screenshots, terminal prompts, or troubleshooting notes). No Linux-specific tools or patterns are mentioned, and there are no notes about potential platform differences.
Recommendations
- When referencing command-line environments, list Bash (Linux/macOS) before or alongside cmd/PowerShell, e.g., 'in a terminal (such as Bash, cmd, or PowerShell)'.
- Add explicit confirmation that all commands work on Linux and macOS, possibly with a note or a screenshot from a Linux terminal.
- Include troubleshooting notes or links for common Linux/macOS issues (e.g., permissions, installing .NET SDK on Linux).
- Where relevant, provide Linux/macOS-specific instructions for environment variable setup or file paths.
- Consider including a sample run or output from a Linux terminal to reinforce cross-platform parity.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/telephony/includes/voice-routing-sdk-portal.md
...kstarts/telephony/includes/voice-routing-sdk-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing .NET regular expressions and linking to .NET documentation for regex, which is a Windows-centric technology. There are no Linux-specific examples or references to cross-platform tools or documentation. The workflow is described entirely through the Azure Portal UI, with no mention of command-line alternatives (such as Azure CLI or Bash scripting) that are common in Linux environments.
Recommendations
- Provide links to general regular expression documentation (such as PCRE or POSIX regex) in addition to or instead of .NET regex documentation.
- Include examples or references for configuring direct routing using cross-platform tools like Azure CLI, Bash, or REST APIs.
- Clarify that the instructions are platform-agnostic if they are, or explicitly mention Linux compatibility where applicable.
- Add notes or sections for Linux users, especially if any steps differ or if there are recommended tools for Linux environments.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-answer-teams-calls.md
...ts/tpe/teams-phone-extensibility-answer-teams-calls.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell commands for key setup steps (e.g., creating Teams resource accounts, associating resources, and hosting DevTunnels). There are no equivalent Linux/bash examples or references to cross-platform alternatives. Windows tools and patterns (PowerShell, devtunnel CLI) are mentioned exclusively or before any Linux equivalents, and the prerequisites and instructions assume a Windows environment.
Recommendations
- Provide bash or Azure CLI equivalents for all PowerShell commands, especially for creating and associating Teams resource accounts.
- Clarify whether DevTunnels and related CLI commands are available and supported on Linux/macOS, and provide installation/usage instructions for those platforms.
- Add explicit notes or sections for Linux/macOS users, including troubleshooting tips and environment setup guidance.
- Where possible, use cross-platform tools (e.g., Azure CLI, REST API calls) in examples, or show both Windows and Linux command variants side-by-side.
- Review all links to ensure they do not point exclusively to Windows/Powershell documentation, and add references to Linux-compatible documentation where available.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-access-teams-phone.md
...ts/tpe/teams-phone-extensibility-access-teams-phone.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (such as the Microsoft 365 admin center UI and the Get-CsOnlineApplicationInstance PowerShell cmdlet) without providing Linux or cross-platform alternatives. The instructions for enabling Teams for a user are given only via the Microsoft 365 admin center, which is a web UI but is often described in a way that assumes a Windows-centric workflow. The only command-line tool mentioned is a PowerShell cmdlet, with no mention of equivalent Graph API or CLI commands usable from Linux/macOS. There are no explicit Linux or cross-platform command-line examples for user or resource account management.
Recommendations
- Provide equivalent examples using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST API for all operations currently described with PowerShell cmdlets.
- When referencing the Microsoft 365 admin center, clarify that it is a web-based tool accessible from any OS, and consider linking to equivalent command-line or API-based instructions.
- List Linux/cross-platform methods before or alongside Windows/PowerShell methods to avoid 'windows_first' ordering.
- Explicitly mention that all REST API examples are OS-agnostic and can be used from any platform.
- Where possible, add bash/cURL or Azure CLI examples for provisioning and consent operations.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/tpe/teams-phone-extensibility-server-outbound-call.md
.../tpe/teams-phone-extensibility-server-outbound-call.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 the Microsoft Admin portal and Marketplace workflows, which are primarily accessed via web interfaces commonly used in Windows-centric enterprise environments. There are no Linux-specific instructions or command-line examples (e.g., Azure CLI, Bash, or PowerShell Core on Linux) for license assignment or resource management. The code example is in C#, a language most often associated with Windows development, and there are no alternative examples for Linux-preferred languages (e.g., Python, Node.js). No mention is made of Linux-compatible tools or patterns for managing Teams resources or licenses.
Recommendations
- Include Azure CLI and/or REST API examples for license assignment and resource management, which are platform-agnostic and work on Linux.
- Provide code samples in additional languages commonly used on Linux (e.g., Python, Node.js) alongside C#.
- Explicitly mention that all steps can be performed from Linux environments and provide guidance for Linux users (e.g., using browser-based portals from Linux, or using CLI tools).
- Reference PowerShell Core (pwsh), which is cross-platform, if scripting is required, and provide equivalent Bash scripts where possible.
- Add a section or note on Linux compatibility and best practices for cross-platform automation.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/get-started-with-video-calling.md
.../voice-video-calling/get-started-with-video-calling.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, particularly in the 'Clean up resources' section, where only Windows is mentioned in the link to cleaning up resources. There are no explicit Linux or cross-platform CLI examples or references, and the tabs and pivots focus on Windows without mentioning Linux. This may make Linux users feel unsupported or overlooked.
Recommendations
- Add explicit Linux (and macOS, if relevant) instructions or tabs for resource cleanup and other platform-agnostic tasks.
- Ensure that all references to command-line tools or scripts include both Windows (PowerShell/Command Prompt) and Linux (Bash/CLI) equivalents.
- Update links and tabbed content to include Linux pivots where applicable, or clarify if certain features are Windows-only.
- Review included content files (e.g., video-calling-javascript.md) to ensure parity in platform coverage and examples.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/closed-captions/closed-captions-ios.md
...alling/includes/closed-captions/closed-captions-ios.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tabs and pivots in prerequisite and cleanup links (e.g., '?tabs=windows', '?pivots=platform-azp'), and does not mention or provide Linux or cross-platform alternatives for resource creation or management. All code examples are iOS/Swift-focused, but ancillary Azure resource management instructions are Windows-centric.
Recommendations
- Update prerequisite and cleanup links to include or prioritize Linux and macOS instructions/tabs alongside Windows.
- Ensure that quickstart and resource creation guides referenced support Linux (e.g., Azure CLI, Bash) and are clearly linked.
- Avoid using Windows-specific query parameters (e.g., '?tabs=windows') in links unless alternatives are also provided.
- Explicitly state cross-platform options for Azure resource management, such as Azure CLI or the Azure Portal, not just Windows tools.
- Add a note clarifying that all features and setup steps are available on non-Windows platforms where applicable.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-ios.md
...ludes/teams-auto-attendant/teams-auto-attendant-ios.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively referencing the Teams Admin Center (a web-based tool but often associated with Windows environments), Microsoft Graph Explorer, and Azure CLI. While the quickstart is for iOS development (macOS), all instructions for Teams configuration and resource management are given using Microsoft-centric tools, with no mention of Linux alternatives or command-line approaches (e.g., PowerShell, bash scripts, or cross-platform REST API usage). There are no Linux-specific examples or guidance for users who may not have access to the Teams Admin Center or prefer CLI/REST approaches.
Recommendations
- Provide equivalent instructions for configuring Teams Auto Attendant and retrieving Object IDs using cross-platform tools such as the Microsoft Graph API via curl or other REST clients.
- Explicitly mention that Teams Admin Center is web-based and accessible from any OS, and provide links to REST API documentation for users who prefer or require command-line or programmatic access.
- Add Linux/macOS CLI examples (e.g., using curl or httpie) for interacting with Microsoft Graph to retrieve resource information.
- Clarify any steps that are platform-agnostic and ensure parity in instructions for users on Linux or other non-Windows platforms.
- Where Azure CLI is used, confirm that all commands work identically on Linux/macOS and note any platform-specific caveats.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-auto-attendant/teams-auto-attendant-android.md
...s/teams-auto-attendant/teams-auto-attendant-android.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Teams Admin Center (a web-based tool, but often associated with Windows environments) and Microsoft Graph Explorer for administrative tasks, without mentioning or providing alternatives for Linux users. There are no examples or instructions for performing equivalent tasks using Linux-friendly tools (e.g., Azure CLI, Microsoft Graph CLI, or REST API via curl). Additionally, the documentation refers to the Teams Admin Center before any mention of CLI or API-based approaches, reinforcing a 'windows_first' pattern. No PowerShell-specific commands are present, but the overall workflow assumes familiarity with Microsoft-centric, often Windows-preferred, tools.
Recommendations
- Provide alternative instructions for Linux users, such as using Microsoft Graph CLI or REST API (with curl) to retrieve the Auto Attendant Object ID and related information.
- Explicitly mention that the Teams Admin Center is web-based and accessible from any OS, but also offer CLI/API alternatives for users who prefer or require non-GUI workflows.
- When referencing tools or workflows, present cross-platform options (e.g., Azure CLI, Graph CLI) alongside or before Windows-centric tools.
- Add Linux/macOS-specific notes or examples where relevant, especially for administrative and setup steps.
- Ensure parity in all code and command-line examples by including both Windows and Linux-friendly commands where applicable.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-ios.md
...ling/includes/teams-call-queue/teams-call-queue-ios.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing Windows-centric tools and workflows, such as the Teams Admin Center and Microsoft Graph Explorer, without mentioning or providing Linux equivalents or alternatives. Steps for obtaining necessary information (e.g., Call Queue Object ID) rely on Windows-based portals and tools, and there are no examples or instructions for performing these tasks on Linux or cross-platform environments. The Azure CLI is mentioned for token generation, which is cross-platform, but all other administrative steps are Windows-focused.
Recommendations
- Provide instructions for accessing Teams Admin features via cross-platform tools (e.g., Microsoft Graph API via CLI or REST calls) instead of relying solely on Teams Admin Center.
- Include Linux-friendly examples for administrative tasks, such as using curl or PowerShell Core (pwsh) on Linux to interact with Microsoft Graph.
- Mention and demonstrate how to use browser-based portals on Linux, or clarify that Teams Admin Center is accessible from any OS via web browser.
- Add explicit notes or sections for Linux users, highlighting any OS-agnostic steps and providing alternatives where Windows-only tools are referenced.
- Ensure that any screenshots or step-by-step instructions do not assume a Windows environment unless absolutely necessary.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-android.md
.../includes/teams-call-queue/teams-call-queue-android.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows, such as the Teams Admin Center and Microsoft Graph Explorer, without mentioning Linux alternatives or command-line options. All administrative steps (creating call queues, finding object IDs) are described using GUI tools that are only available on Windows, and there are no examples or instructions for performing these tasks on Linux or via cross-platform command-line tools. The Azure CLI example is cross-platform, but it is only used for token generation, not for Teams or Call Queue management.
Recommendations
- Provide equivalent instructions for managing Teams Call Queues and Resource Accounts using PowerShell, Azure CLI, or Microsoft Graph API scripts that can be run on Linux/macOS.
- Include examples of using Microsoft Graph API via curl or other cross-platform tools to retrieve Object IDs, rather than relying solely on the Graph Explorer web tool.
- Mention and link to any available cross-platform admin tools or document how to perform necessary steps without requiring Windows-only GUIs.
- Clearly indicate which steps require Windows and offer alternatives or workarounds for Linux users where possible.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-call-queue/teams-call-queue-javascript.md
...cludes/teams-call-queue/teams-call-queue-javascript.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by referencing Windows-specific tools and patterns, such as the Teams Admin Center and Microsoft Graph Explorer, without mentioning or providing Linux equivalents or alternatives. The instructions for creating resources link to pages with Windows pivots/tabs by default. There are no explicit Linux or cross-platform command-line examples for administrative tasks, and the documentation assumes the use of a GUI (Teams Admin Center), which is more common on Windows. No PowerShell-specific commands are present, but the absence of Linux CLI or automation alternatives is notable.
Recommendations
- Provide Linux-friendly alternatives for administrative steps, such as using Azure CLI, Microsoft Graph API via curl, or cross-platform scripts, instead of relying solely on Teams Admin Center (GUI).
- When linking to resource creation guides, ensure that Linux and macOS options are equally visible and not defaulted to Windows.
- Explicitly state that all Node.js and npm commands are cross-platform, and verify that all instructions work on Linux/macOS shells.
- Add examples or notes for obtaining the Call Queue Object ID and other administrative data using command-line tools or scripts that can be run on Linux.
- Where screenshots or instructions reference GUI tools, provide equivalent CLI/API instructions for users on non-Windows systems.
Communication Services
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/quickstarts/voice-video-calling/includes/teams-user/teams-user-ios.md
...ce-video-calling/includes/teams-user/teams-user-ios.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates Windows bias primarily in the prerequisites section, where enabling Teams Phone features for users is referenced via a PowerShell link, with no mention of Linux or cross-platform alternatives. The Teams deployment link also points to Windows-centric installation instructions. No Linux or macOS equivalents for Teams management or deployment are mentioned, and the only administrative tooling referenced is PowerShell, which is Windows-specific.
Recommendations
- Include instructions or links for managing Teams Phone licenses and enabling Enterprise Voice using cross-platform tools (e.g., Microsoft Graph API, Teams Admin Center web UI).
- Mention that PowerShell is Windows-specific and provide alternatives for Linux/macOS users.
- Add references to Teams deployment guides for macOS and Linux, or clarify platform requirements.
- Where possible, provide parity in administrative examples, ensuring Linux/macOS users are not excluded from setup steps.