Document Details

Create Communication Resource
Home / Scan #48 / Create Communication Resource
Sad Tux - Windows bias detected
This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

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.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2026-01-12 00:00 #99 completed Biased Biased
2026-01-11 06:20 #98 completed Biased Biased
2026-01-10 00:00 #92 completed Clean Clean
2026-01-06 22:28 #78 completed Clean Clean
2025-12-29 18:00 #48 cancelled Biased Biased
2025-12-15 00:00 #7 completed Clean Clean
2025-12-14 05:05 #6 completed Clean Clean

Flagged Code Snippets

## Store your connection string

Communication Services SDKs use connection strings to authorize requests made to Communication Services. You have several options for storing your connection string:

* An application running on the desktop or on a device can store the connection string in an **app.config** or **web.config** file. Add the connection string to the **AppSettings** section in these files.
* An application running in an Azure App Service can store the connection string in the [App Service application settings](../../app-service/configure-common.md). Add the connection string to the **Connection Strings** section of the Application Settings tab within the portal.
* You can store your connection string in [Azure Key Vault](../../data-factory/store-credentials-in-key-vault.md). You can further securely [manage your connection string](../../storage/common/storage-account-keys-manage.md).
* If you're running your application locally, you may want to store your connection string in an environment variable.

### Store your connection string in an environment variable

To configure an environment variable, open a console window and select your operating system from the following tabs. Replace `<yourconnectionstring>` with your actual connection string.

#### [Windows](#tab/windows)

Open a console window and enter the following command: