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:
⚠️
powershell_heavy
⚠️
windows_first
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation exclusively uses PowerShell and Windows-centric tooling (Invoke-RestMethod, PowerShell variables, and operators) for all examples and workflows. There are no equivalent examples for Linux users (e.g., using Bash, curl, or Azure CLI), and the documentation assumes familiarity with Windows scripting patterns. This creates a clear bias towards Windows environments and leaves Linux users without guidance.
Recommendations:
- Provide equivalent Linux/Bash examples using curl or Azure CLI for all PowerShell commands.
- Introduce cross-platform Azure CLI examples, which are supported on both Windows and Linux.
- Explicitly mention that the steps can be performed from any OS, and clarify any OS-specific requirements.
- Structure example sections so that both Windows (PowerShell) and Linux (Bash/CLI) users can easily find relevant instructions.
- Avoid using Windows-specific operators (such as -replace) without showing the equivalent in Bash or other shells.
Create pull request
Flagged Code Snippets
Now that we have changed the Location value, this updated Configuration Profile will be created in Western Europe when we submit it.
## Creating the new profile in the desired location
All that remains now is to `PUT` this new profile, using `Invoke-RestMethod` once more.
## Adjusting the location
Creating the profile in a new location is as simple as changing the `Location` property to our desired Azure Region.
We also will need to create a new name for this profile. Let's change the name of the Configuration Profile `profileUk`. We should update the `Name` property within the profile, and also in the URL. We can use the `-replace` format operator to make this simple.