Document Details
Azure Api Fhir Resource Manager Template
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
windows_first
powershell_heavy
windows_tools
Summary
The documentation demonstrates a mild Windows bias by listing PowerShell instructions before CLI/Bash, emphasizing Azure PowerShell (a Windows-centric tool), and suggesting Git Bash (from Git for Windows) as the Bash shell example for CLI users. While Linux/Bash usage is supported via the Azure CLI, the documentation's ordering and tool recommendations subtly prioritize Windows environments.
Recommendations
- Alternate the order of PowerShell and CLI/Bash instructions or present CLI/Bash first to balance platform emphasis.
- In the prerequisites for CLI, mention native Bash shells on Linux/macOS before or alongside Git Bash for Windows.
- Explicitly state that all CLI examples work natively on Linux/macOS terminals, not just in Git Bash or Windows environments.
- Where possible, provide cross-platform notes or highlight any differences in command usage between Windows and Linux/macOS.
- Consider adding a short section or callout confirming full support for Linux/macOS environments to reassure non-Windows users.
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-09-11 00:00 | #108 | completed |
Clean
|
| 2025-08-11 00:00 | #77 | completed |
Clean
|
| 2025-08-10 00:00 | #76 | completed |
Clean
|
| 2025-08-09 00:00 | #75 | completed |
Clean
|
| 2025-08-08 00:00 | #74 | completed |
Clean
|
| 2025-08-07 00:00 | #73 | completed |
Clean
|
| 2025-08-06 00:00 | #72 | completed |
Clean
|
| 2025-08-05 00:00 | #71 | completed |
Clean
|
| 2025-08-03 00:00 | #69 | completed |
Clean
|
| 2025-08-01 00:00 | #67 | completed |
Clean
|
| 2025-07-31 00:00 | #66 | completed |
Clean
|
| 2025-07-30 00:00 | #65 | completed |
Clean
|
| 2025-07-29 00:01 | #64 | completed |
Clean
|
| 2025-07-28 00:00 | #63 | completed |
Clean
|
| 2025-07-27 00:00 | #62 | completed |
Clean
|
| 2025-07-26 00:01 | #61 | completed |
Clean
|
| 2025-07-25 00:00 | #60 | completed |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
--- > [!NOTE] > The deployment takes a few minutes to complete. Note the names for the Azure API for FHIR service and the resource group, for use in reviewing deployed resources. ## Review deployed resources # [Portal](#tab/azure-portal) Follow these steps to see an overview of your new Azure API for FHIR service: 1. In the [Azure portal](https://portal.azure.com), search for and select **Azure API for FHIR**. 2. In the FHIR list, select your new service. The **Overview** page for the new Azure API for FHIR service appears. 3. To validate that the new FHIR API account is provisioned, select the link next to **FHIR metadata endpoint** to fetch the FHIR API capability statement. The link has a format of `https://<service-name>.azurehealthcareapis.com/metadata`. If the account is provisioned, a JSON file is displayed. # [PowerShell](#tab/PowerShell) Run the following interactive code to view details about your Azure API for FHIR service. You have to enter the name and resource group of the new service.
--- ## Clean up resources When no longer needed, delete the resource group. This deletes the resources in the resource group. # [Portal](#tab/azure-portal) 1. In the [Azure portal](https://portal.azure.com), search for and select **Resource groups**. 2. In the resource group list, choose the name of your resource group. 3. In the **Overview** page of your resource group, select **Delete resource group**. 4. In the confirmation dialog box, type the name of your resource group, and then select **Delete**. # [PowerShell](#tab/PowerShell)