About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation exhibits a Windows bias by prioritizing Windows-specific instructions and tools, such as PowerShell and WSL, and by providing more detailed, step-by-step guidance for Windows users. Linux and macOS instructions are less detailed and often grouped together, with some steps (like directory navigation) omitted. There is also a focus on Docker Desktop, which is more common on Windows, and explicit notes about Windows path conventions, while Linux equivalents are not discussed.
Recommendations:
- Provide equally detailed, step-by-step instructions for Linux and macOS users, including terminal commands for directory navigation and script execution.
- List Linux and macOS instructions before or alongside Windows instructions, rather than after.
- Include Linux-native Docker installation links and prerequisites, not just Docker Desktop (which is Windows/macOS-centric).
- Offer explicit examples of file path conventions for Linux/macOS in addition to Windows.
- Avoid requiring WSL for Windows users unless absolutely necessary, and clarify when native Linux/macOS environments are supported.
- Ensure that all scripts and commands are shown in both PowerShell (Windows) and Bash (Linux/macOS) formats where applicable.
Create pull request
Flagged Code Snippets
cd <path to your common scripts folder> # Update this path
2. Issue wsl command to open WSL at this directory.
The argument `ACCEPT_EULA` confirms the [Microsoft Software License Terms](https://github.com/Azure/azure-event-hubs-emulator-installer/blob/main/EMULATOR_EULA.md). Be sure to place the .env file in the same directory as the *docker-compose.yaml* file.
> [!IMPORTANT]
> When you're specifying file paths in Windows, use double backslashes (`\\`) instead of single backslashes (`\`) to avoid confusion with escape characters.
4. To run the emulator, execute the following command:
- Application containers on the different bridge network can interact with Emulator using the "host.docker.internal" as host. Use following connection string: