Skip to content

Commit 91b0e6d

Browse files
committed
update landing page links
1 parent c3d5c84 commit 91b0e6d

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/firmware-analysis/firmware-analysis-rbac.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In Firmware analysis, the most common roles are Owner, Contributor, Security Adm
2222
Azure organizes resources into resource hierarchies, which are in a top-down structure, and you can assign roles at each level of the hierarchy. The level at which you assign a role is the "scope," and lower scopes may inherit roles assigned at higher scopes. Learn more about the [levels of hierarchy and how to organize your resources in the hierarchy](/azure/cloud-adoption-framework/ready/azure-setup-guide/organize-resources).
2323

2424
When you onboard your subscription to Firmware analysis and select your resource group, the action automatically creates the **default** resource within your resource group.
25-
25+
2626
Navigate to your resource group and select **Show hidden types** to show the **default** resource. The **default** resource has the **Microsoft.IoTFirmwareDefense.workspaces** type.
2727

2828
:::image type="content" source="media/firmware-analysis-rbac/default-workspace.png" alt-text="Screenshot of the toggle button 'Show hidden types' that reveals a resource named 'default'." lightbox="media/firmware-analysis-rbac/default-workspace.png":::

articles/firmware-analysis/index.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ landingContent:
2626
- text: Get started with Firmware analysis in the Azure portal
2727
url: tutorial-analyze-firmware.md
2828
- text: What file systems are supported by Firmware analysis?
29-
url: firmware-analysis-faq.md#What-types-of-firmware-images-does-Firmware-analysis-support
29+
url: firmware-analysis-faq.md#what-types-of-firmware-images-does-firmware-analysis-support
3030
- linkListType: concept
3131
links:
3232
- text: What roles and permissions are needed to use Firmware analysis?
@@ -39,14 +39,14 @@ landingContent:
3939
# Card
4040
- title: Automate your workflow
4141
linkLists:
42-
- linkListType: how-to-guides
42+
- linkListType: how-to-guide
4343
links:
4444
- text: Automate your workflow using service principals
4545
url: automate-firmware-analysis-service-principals.md
4646
- text: Analyze firmware images using Azure CLI commands
4747
url: quickstart-upload-firmware-using-azure-command-line-interface.md
4848
- text: Analyze firmware images using Azure PowerShell commands
49-
url: quickstart-upload-firmware-using-azure-powershell.md
49+
url: quickstart-upload-firmware-using-powershell.md
5050
- text: Analyze firmware images using a Python script
5151
url: quickstart-upload-firmware-using-python.md
5252

@@ -56,7 +56,7 @@ landingContent:
5656
- linkListType: concept
5757
links:
5858
- text: Understand the resource hierarchy of Firmware analysis
59-
url: firmware-analysis-rbac.md#Understanding-the-Representation-of-Firmware-Images-in-the-Azure-Resource-Hierarchy
59+
url: firmware-analysis-rbac.md#understanding-the-representation-of-firmware-images-in-the-azure-resource-hierarchy
6060
- text: Understand and interpret the extractor path results
6161
url: interpreting-extractor-paths.md
6262

0 commit comments

Comments
 (0)