Merge pull request #294026 from karengu0/update-name-case

Update 'firmware analysis' casing

Author: v-shils

articles/firmware-analysis/automate-firmware-analysis-service-principals.md

@@ -1,14 +1,14 @@
 ---
-title: Use service principals to automate workflows in Firmware analysis
-description: Learn about how to use service principals to automate workflows for Firmware Analysis.
+title: Use service principals to automate workflows in firmware analysis
+description: Learn about how to use service principals to automate workflows for firmware analysis.
 author: karengu0
 ms.author: karenguo
 ms.topic: conceptual
 ms.date: 11/04/2024
 ms.service: azure
 ---
 
-# How to Use Service Principals to Automate Workflows in Firmware analysis
+# How to Use Service Principals to Automate Workflows in firmware analysis
 
 Many users of the firmware analysis service may need to automate their workflow. The command `az login` creates an interactive login experience with two-factor authentication that makes it difficult for users to fully automate their workflow. A [service principal](/entra/identity-platform/app-objects-and-service-principals) is a secure identity with proper permissions that authenticates to Azure in the command line without requiring two-factor authentication or an interactive log-in. This article explains how to create a service principal and use it to interact with the firmware analysis service. For more information on creating service principals, visit [Create Azure service principals using the Azure CLI](/cli/azure/azure-cli-sp-tutorial-1#create-a-service-principal). To authenticate securely, we recommend creating a service principal and authenticating using certificates. To learn more, visit [Create a service principal containing a certificate using Azure CLI](/cli/azure/azure-cli-sp-tutorial-3).
 
@@ -44,9 +44,12 @@ Many users of the firmware analysis service may need to automate their workflow.
     az login --service-principal --username <CLIENT_ID> --password <SECRET> --tenant <TENANT_ID>
     ```
 
-6.	Once logged in, refer to the following Quickstarts for scripts to interact with the Firmware analysis service via Azure PowerShell, Azure CLI, or Python:
+6.	Once logged in, refer to the following Quickstarts for scripts to interact with the firmware analysis service via Azure PowerShell, Azure CLI, or Python:
     - [Upload firmware using Azure CLI](quickstart-upload-firmware-using-azure-command-line-interface.md)
     - [Upload firmware using Azure PowerShell](quickstart-upload-firmware-using-powershell.md)
     - [Upload firmware using Python](quickstart-upload-firmware-using-python.md)
+ 
 
-
+#test
+test
+test

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

@@ -1,52 +1,52 @@
 ---
-title: Azure Role-Based Access Control for Firmware analysis
-description: Learn about how to use Azure Role-Based Access Control for Firmware Analysis.
+title: Azure Role-Based Access Control for firmware analysis
+description: Learn about how to use Azure Role-Based Access Control for firmware analysis.
 author: karengu0
 ms.author: karenguo
 ms.topic: conceptual
 ms.date: 01/10/2024
 ms.service: azure
 ---
 
-# Overview of Azure Role-Based Access Control for Firmware analysis
-As a user of Firmware analysis, you may want to manage access to your firmware image analysis results. Azure Role-Based Access Control (RBAC) is an authorization system that enables you to control who has access to your analysis results, what permissions they have, and at what level of the resource hierarchy. This article explains how to store firmware analysis results in Azure, manage access permissions, and use RBAC to share these results within your organization and with third parties. To learn more about Azure RBAC, visit [What is Azure Role-Based Access Control (Azure RBAC)?](./../role-based-access-control/overview.md).
+# Overview of Azure Role-Based Access Control for firmware analysis
+As a user of firmware analysis, you may want to manage access to your firmware image analysis results. Azure Role-Based Access Control (RBAC) is an authorization system that enables you to control who has access to your analysis results, what permissions they have, and at what level of the resource hierarchy. This article explains how to store firmware analysis results in Azure, manage access permissions, and use RBAC to share these results within your organization and with third parties. To learn more about Azure RBAC, visit [What is Azure Role-Based Access Control (Azure RBAC)?](./../role-based-access-control/overview.md).
 
 ## Roles
 Roles are a collection of permissions packaged together. There are two types of roles:
 
 * **Job function roles** give users permission to perform specific job functions or tasks, such as **Key Vault Contributor** or **Azure Kubernetes Service Cluster Monitoring User**. 
 * **Privileged administrator roles** give elevated access privileges, such as **Owner**, **Contributor**, or **User Access Administrator**. To learn more about roles, visit [Azure built-in roles](./../role-based-access-control/built-in-roles.md).
 
-In Firmware analysis, the most common roles are Owner, Contributor, Security Admin, and Firmware Analysis Admin. Learn more about [which roles you need for different permissions](./firmware-analysis-rbac.md#firmware-analysis-roles-scopes-and-capabilities), such as uploading firmware images or sharing firmware analysis results.
+In firmware analysis, the most common roles are Owner, Contributor, Security Admin, and Firmware Analysis Admin. Learn more about [which roles you need for different permissions](./firmware-analysis-rbac.md#firmware-analysis-roles-scopes-and-capabilities), such as uploading firmware images or sharing firmware analysis results.
 
 ## Understanding the Representation of Firmware Images in the Azure Resource Hierarchy
 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).
 
-When you onboard your subscription to Firmware analysis and select your resource group, the action automatically creates the **default** resource within your resource group.
+When you onboard your subscription to firmware analysis and select your resource group, the action automatically creates the **default** resource within your resource group.
 
 Navigate to your resource group and select **Show hidden types** to show the **default** resource. The **default** resource has the **Microsoft.IoTFirmwareDefense.workspaces** type.
 
 :::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":::
 
 Although the **default** workspace resource isn't something that you'll regularly interact with, each firmware image that you upload will be represented as a resource and stored here.
 
-You can use RBAC at each level of the hierarchy, including at the hidden **default Firmware Analysis Workspace** resource level. 
+You can use RBAC at each level of the hierarchy, including at the hidden **default firmware analysis workspace** resource level. 
 
-Here's the resource hierarchy of Firmware Analysis:
+Here's the resource hierarchy of firmware analysis:
 
 :::image type="content" source="media/firmware-analysis-rbac/resource-hierarchy.png" alt-text="Diagram that shows the resource hierarchy of firmware images of Firmware Analysis." lightbox="media/firmware-analysis-rbac/resource-hierarchy.png":::
 
 ## Apply Azure RBAC
 
 > [!Note]
-> To begin using Firmware analysis, the user that onboards the subscription onto Firmware analysis ***must be*** an Owner, Contributor, Firmware Analysis Admin, or Security Admin at the subscription level. Follow the tutorial at [Analyze a firmware image with Firmware analysis](./tutorial-analyze-firmware.md#onboard-your-subscription-to-use-firmware-analysis) to onboard your subscription. Once you've onboarded your subscription, a user only needs to be a Firmware Analysis Admin to use Firmware Analysis.
+> To begin using firmware analysis, the user that onboards the subscription onto firmware analysis ***must be*** an Owner, Contributor, Firmware Analysis Admin, or Security Admin at the subscription level. Follow the tutorial at [Analyze a firmware image with firmware analysis](./tutorial-analyze-firmware.md#onboard-your-subscription-to-use-firmware-analysis) to onboard your subscription. Once you've onboarded your subscription, a user only needs to be a Firmware Analysis Admin to use firmware analysis.
 > 
 
-As a user of Firmware analysis, you may need to perform certain actions for your organization, such as uploading firmware images or sharing analysis results.
+As a user of firmware analysis, you may need to perform certain actions for your organization, such as uploading firmware images or sharing analysis results.
 
-Actions like these involve Role-Based Access Control (RBAC). To effectively use RBAC for Firmware analysis, you must know what your role assignment is, and at what scope. Knowing this information will inform you about what permissions you have, and thus whether you can complete certain actions. To check your role assignment, refer to [Check access for a user to a single Azure resource - Azure RBAC](./../role-based-access-control/check-access.md). Next, see the following table to check what roles and scopes are necessary for certain actions.
+Actions like these involve Role-Based Access Control (RBAC). To effectively use RBAC for firmware analysis, you must know what your role assignment is, and at what scope. Knowing this information will inform you about what permissions you have, and thus whether you can complete certain actions. To check your role assignment, refer to [Check access for a user to a single Azure resource - Azure RBAC](./../role-based-access-control/check-access.md). Next, see the following table to check what roles and scopes are necessary for certain actions.
 
-### Common roles in Firmware analysis
+### Common roles in firmware analysis
 
 This table categorizes each role and provides a brief description of their permissions:
 
@@ -70,7 +70,7 @@ Invite users to the Subscription | Owner at the **Subscription** level (Owner at
 ## Uploading Firmware images
 To upload firmware images:
 
-* Confirm that you have sufficient permission in [Firmware Analysis Roles, Scopes, and Capabilities](#firmware-analysis-roles-scopes-and-capabilities).
+* Confirm that you have sufficient permission in [Firmware analysis Roles, Scopes, and Capabilities](#firmware-analysis-roles-scopes-and-capabilities).
 * [Upload a firmware image for analysis](./tutorial-analyze-firmware.md#upload-a-firmware-image-for-analysis).
 
 ## Invite third parties to interact with your firmware analysis results

articles/firmware-analysis/index.yml

@@ -10,26 +10,27 @@ metadata:
   author: karengu0
   ms.author: karenguo
   ms.date: 11/11/2024
+  ms.service: azure
 
 
 landingContent:
-  - title: Get started
+  - title: Get started 
     linkLists:
       - linkListType: get-started
         links:
-          - text: What is Firmware analysis (preview)?
+          - text: What is firmware analysis (preview)?
             url: overview-firmware-analysis.md
-          - text: Get started with Firmware analysis in the Azure portal
+          - text: Get started with firmware analysis in the Azure portal
             url: tutorial-analyze-firmware.md
-          - text: What file systems are supported by Firmware analysis?
+          - text: What file systems are supported by firmware analysis?
             url: firmware-analysis-faq.md#what-types-of-firmware-images-does-firmware-analysis-support
       - linkListType: concept
         links:
-          - text: What roles and permissions are needed to use Firmware analysis?
+          - text: What roles and permissions are needed to use firmware analysis?
             url: firmware-analysis-rbac.md
       - linkListType: whats-new
         links:
-          - text: What's new in Firmware analysis (preview)?
+          - text: What's new in firmware analysis (preview)?
             url: release-notes.md
 
   - title: Automate your workflow
@@ -45,11 +46,11 @@ landingContent:
           - text: Analyze firmware images using a Python script
             url: quickstart-upload-firmware-using-python.md
 
-  - title: Understand the Firmware analysis service
+  - title: Understand the firmware analysis service
     linkLists:
       - linkListType: concept
         links:
-          - text: Understand the resource hierarchy of Firmware analysis
+          - text: Understand the resource hierarchy of firmware analysis
             url: firmware-analysis-rbac.md#understanding-the-representation-of-firmware-images-in-the-azure-resource-hierarchy
           - text: Understand and interpret the extractor path results
             url: interpreting-extractor-paths.md

articles/firmware-analysis/toc.yml

@@ -3,7 +3,7 @@
 
 - name: "Overview"
   items:
-  - name: Overview of Firmware analysis (preview)
+  - name: Overview of firmware analysis (preview)
     href: overview-firmware-analysis.md
   - name: Firmware analysis frequently asked questions
     href: firmware-analysis-faq.md
@@ -12,14 +12,14 @@
   expanded: true
 - name: Quickstarts
   items:
-  - name: Quickstart to use Firmware analysis with Azure CLI
+  - name: Quickstart to use firmware analysis with Azure CLI
     href: quickstart-upload-firmware-using-azure-command-line-interface.md
-  - name: Quickstart to use Firmware analysis with Azure PowerShell
+  - name: Quickstart to use firmware analysis with Azure PowerShell
     href: quickstart-upload-firmware-using-powershell.md
-  - name: Quickstart to use Firmware analysis with a Python script
+  - name: Quickstart to use firmware analysis with a Python script
     href: quickstart-upload-firmware-using-python.md
   expanded: true
-- name: Tutorial using Firmware analysis with the Azure portal
+- name: Tutorial using firmware analysis with the Azure portal
   href: tutorial-analyze-firmware.md
 - name: Concepts
   items: