Document Details
Create Blueprint Rest Api
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.
Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell examples for making REST API calls, recommending PowerShell as the tool of choice, and omitting equivalent Linux/macOS command-line examples (such as curl or HTTPie). The guidance assumes familiarity with PowerShell cmdlets and Windows-centric tooling, with no mention of cross-platform alternatives or how to perform the same tasks on Linux or macOS.
Recommendations
- Add equivalent examples using curl or HTTPie for making REST API calls, which are available on Linux, macOS, and Windows.
- Mention cross-platform tools (e.g., Azure CLI, REST clients like Postman, or ARMClient) alongside PowerShell, and provide sample usage.
- Rephrase guidance to avoid recommending PowerShell as the default or only tool, instead offering a choice of tools for different platforms.
- Include notes or sections specifically for Linux/macOS users, ensuring parity in authentication and REST invocation instructions.
- Where PowerShell-specific cmdlets are referenced (e.g., ConvertFrom-Json), provide equivalent commands for bash/jq or other common Linux utilities.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
Flagged Code Snippets
Replace `{subscriptionId}` in the preceding `$restUri` variable to get information about your
subscription. The `$response` variable holds the result of the `Invoke-RestMethod` cmdlet, which you can parse with cmdlets such as [ConvertFrom-Json](/powershell/module/microsoft.powershell.utility/convertfrom-json). If the REST API service endpoint expects a `Request Body`, provide a JSON-formatted variable to the `-Body` parameter of `Invoke-RestMethod`.
## Create a blueprint
The first step in defining a standard pattern for compliance is to compose a blueprint from the
available resources. Let's create a blueprint named *MyBlueprint* to configure role and policy
assignments for the subscription. Then you add a resource group, an ARM template, and a role
assignment on the resource group.
> [!NOTE]
> When you're using the REST API, the _blueprint_ object is created first. For each _artifact_ to be added that has parameters, you define the parameters in advance on the initial *blueprint*.
In each REST API URI, replace the following variables with your own values:
- `{YourMG}` - Replace with the ID of your management group.
- `{subscriptionId}` - Replace with your subscription ID.
> [!NOTE]
> You can also create blueprints at the subscription level. For more information, see
> [create blueprint at subscription example](/rest/api/blueprints/blueprints/createorupdate#subscriptionblueprint).
1. Create the initial _blueprint_ object. The `Request Body` includes properties about the
blueprint, any resource groups to create, and all of the blueprint-level parameters. You set the parameters during assignment, and they're used by the artifacts you add in later steps.
- REST API URI