update1

LiSeda · LiSeda · commit d39ed385363d · 2025-07-03T17:25:24.000-07:00
diff --git a/learn-pr/achievements/bicep/build-reusable-bicep-files-parameters-social.png b/learn-pr/achievements/bicep/build-reusable-bicep-files-parameters-social.png
diff --git a/learn-pr/achievements/bicep/build-reusable-bicep-files-parameters.svg b/learn-pr/achievements/bicep/build-reusable-bicep-files-parameters.svg
diff --git a/learn-pr/achievements/learn.azure.bicep-conditions-loops.badge.yml b/learn-pr/achievements/learn.azure.bicep-conditions-loops.badge.yml
@@ -2,6 +2,6 @@
 achievementUid: learn.azure.bicep-conditions-loops.badge
 metadata:
   title: >-
-    Microsoft Badge: Build flexible Bicep templates by using conditions and
+    Microsoft Badge: Build flexible Bicep files by using conditions and
     loops was issued by Microsoft
 socialImageUrl: /training/achievements/bicep/bicep-conditions-loops-social.png
diff --git a/learn-pr/achievements/learn.azure.build-reusable-bicep-templates-parameters.badge.yml b/learn-pr/achievements/learn.azure.build-reusable-bicep-templates-parameters.badge.yml
@@ -1,8 +1,8 @@
 ### YamlMime:AchievementDetail
-achievementUid: learn.azure.build-reusable-bicep-templates-parameters.badge
+achievementUid: learn.azure.build-reusable-bicep-files-parameters.badge
 metadata:
   title: >-
-    Microsoft Badge: Build reusable Bicep templates by using parameters was
+    Microsoft Badge: Build reusable Bicep files by using parameters was
     issued by Microsoft
 socialImageUrl: >-
-  /training/achievements/bicep/build-reusable-bicep-templates-parameters-social.png
+  /training/achievements/bicep/build-reusable-bicep-files-parameters-social.png
diff --git a/learn-pr/aspnetcore/customize-dotnet-aspire-existing-resources/includes/5-create-azure-resources-bicep.md b/learn-pr/aspnetcore/customize-dotnet-aspire-existing-resources/includes/5-create-azure-resources-bicep.md
@@ -78,7 +78,7 @@ azd provision
 azd deploy
 ```
 
-## Using custom Bicep templates
+## Using custom Bicep files
 
 You've seen that you can use the `azd infra synth` command to generate the Bicep files necessary to deploy a .NET Aspire app. You can then modify those Bicep files to alter the deployment. But you can also intervene in the creation of Bicep files earlier, during coding by linking to a Bicep file in the app host project.
 
@@ -132,4 +132,4 @@ In the above code, notice that:
 - [What is Bicep?](/azure/azure-resource-manager/bicep/overview)
 - [Understand the structure and syntax of Bicep files](/azure/azure-resource-manager/bicep/file)
 - [Generate Bicep from .NET Aspire project model](/dotnet/aspire/deployment/azure/aca-deployment-azd-in-depth#generate-bicep-from-net-aspire-project-model)
-- [Use custom Bicep templates](/dotnet/aspire/deployment/azure/custom-bicep-templates)
+- [Use custom Bicep files](/dotnet/aspire/deployment/azure/custom-bicep-templates)
diff --git a/learn-pr/aspnetcore/customize-dotnet-aspire-existing-resources/includes/8-summary.md b/learn-pr/aspnetcore/customize-dotnet-aspire-existing-resources/includes/8-summary.md
@@ -11,4 +11,4 @@ Now that you've completed this module, you can:
 
 - [Use Application Insights for .NET Aspire telemetry](/dotnet/aspire/deployment/azure/application-insights)
 - [Tutorial: Deploy a .NET Aspire project with a Redis Cache to Azure](/dotnet/aspire/caching/caching-integrations-deployment)
-- [Use custom Bicep templates](/dotnet/aspire/deployment/azure/custom-bicep-templates)
+- [Use custom Bicep files](/dotnet/aspire/deployment/azure/custom-bicep-templates)
diff --git a/learn-pr/azure/arm-template-specs/includes/3-create-publish-template-spec.md b/learn-pr/azure/arm-template-specs/includes/3-create-publish-template-spec.md
@@ -44,7 +44,7 @@ After your template is written, instead of submitting the template to Azure for
 
 ::: zone pivot="bicepcli,biceppowershell"
 
-[!INCLUDE [Note that Bicep template specs are not roundtrippable](./code/note-bicep-roundtrip.md)]
+[!INCLUDE [Note that Bicep file specs are not roundtrippable](./code/note-bicep-roundtrip.md)]
 
 ::: zone-end
 
diff --git a/learn-pr/azure/arm-template-specs/includes/6-manage-template-spec.md b/learn-pr/azure/arm-template-specs/includes/6-manage-template-spec.md
@@ -144,7 +144,7 @@ After you publish a template as a template spec, you can *export* it. Exporting
 
 ::: zone pivot="bicepcli,biceppowershell"
 
-[!INCLUDE [Note that Bicep template specs are not roundtrippable](./code/note-bicep-roundtrip.md)]
+[!INCLUDE [Note that Bicep file specs aren't roundtrippable](./code/note-bicep-roundtrip.md)]
 
 ::: zone-end
 
diff --git a/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/7-knowledge-check.yml b/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/7-knowledge-check.yml
@@ -46,7 +46,7 @@ quiz:
     - content: Your client can authenticate, but it receives a warning that the key has expired.
       isCorrect: false
       explanation: After a service principal's key has expired, the key can't be used to authenticate. You'll need to issue a new key.
-  - content: You're creating a service principal to run a pipeline. The pipeline deploys a Bicep template that creates a single storage account. Which of the following options has the least privileged access that you need for your pipeline?
+  - content: You're creating a service principal to run a pipeline. The pipeline deploys a Bicep file that creates a single storage account. Which of the following options has the least privileged access that you need for your pipeline?
     choices:
     - content: |
         **Role definition:** Contributor<br />
diff --git a/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/includes/1-introduction.md b/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/includes/1-introduction.md
@@ -2,7 +2,7 @@ Deployment pipelines need to communicate with Azure so they can create and confi
 
 ## Example scenario
 
-Suppose you're responsible for deploying and configuring the Azure infrastructure at a toy company. You've created a Bicep template to deploy your company's website. Until now, you've been deploying it from your own computer by using command-line tools. You've decided to move the deployment into a pipeline.
+Suppose you're responsible for deploying and configuring the Azure infrastructure at a toy company. You've created a Bicep file to deploy your company's website. Until now, you've been deploying it from your own computer by using command-line tools. You've decided to move the deployment into a pipeline.
 
 One of your colleagues has told you that you'll need to set up a service principal for the deployment pipeline. You need to understand what this is, and then set it up so you can deploy your company's website.
 
@@ -21,7 +21,7 @@ By the end of this module, you'll have an understanding of service principals an
 
 You should be familiar with:
 
-- Creating and deploying basic Bicep templates, including modules.
+- Creating and deploying basic Bicep files, including modules.
 - Azure, including the Azure portal, subscriptions, resource groups, and resource definitions.
 
 To follow along with the exercises in the module, you'll need:
diff --git a/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/includes/2-understand-service-principals.md b/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/includes/2-understand-service-principals.md
@@ -2,17 +2,17 @@ Service principals provide a way to authenticate pipelines, applications, and so
 
 ## Why does a pipeline need to authenticate?
 
-When you deploy a Bicep template, you effectively ask Azure Resource Manager to create or modify your Azure resources. In this example scenario, you've created a Bicep template to deploy your toy company's website. The Bicep template declares resources that include an Azure App Service plan, an app, and an Application Insights instance.
+When you deploy a Bicep file, you effectively ask Azure Resource Manager to create or modify your Azure resources. In this example scenario, you've created a Bicep file to deploy your toy company's website. The Bicep file declares resources that include an Azure App Service plan, an app, and an Application Insights instance.
 
-When you deploy the template, Resource Manager checks whether the resources exist. If they don't, Resource Manager creates them. If any already exist, Resource Manager ensures that their configuration matches the configuration that you specify in the template.
+When you deploy the file, Resource Manager checks whether the resources exist. If they don't, Resource Manager creates them. If any already exist, Resource Manager ensures that their configuration matches the configuration that you specify in the file.
 
-All of these operations require permissions, because they access and modify your Azure resources. The specific permissions needed for deployment will depend on what the template contains. To deploy the example Bicep template for your toy company's website, you need to have the following permissions inside the resource group that you're deploying to:
+All of these operations require permissions, because they access and modify your Azure resources. The specific permissions needed for deployment will depend on what the file contains. To deploy the example Bicep file for your toy company's website, you need to have the following permissions inside the resource group that you're deploying to:
 
 - The ability to create deployments. Deployments are considered to be resources with a type of `Microsoft.Resources/deployments`.
 - The ability to create and modify App Service plans and apps.
 - The ability to create and modify Application Insights instances.
 
-Until now, you've probably deployed your Bicep templates yourself by using the Azure CLI or Azure PowerShell. When you use these tools, you normally use your own user account and authenticate by using your browser. This is called using your own _identity_. When you submit a deployment, Azure verifies that your identity has the necessary permissions to do what your Bicep template specifies.
+Until now, you've probably deployed your Bicep files yourself by using the Azure CLI or Azure PowerShell. When you use these tools, you normally use your own user account and authenticate by using your browser. This is called using your own _identity_. When you submit a deployment, Azure verifies that your identity has the necessary permissions to do what your Bicep file specifies.
 
 After you move to a pipeline, you need to use a different type of identity because the pipeline itself runs deployments, without your direct involvement.
 
diff --git a/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/includes/5-grant-service-principal-access-azure.md b/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/includes/5-grant-service-principal-access-azure.md
@@ -50,7 +50,7 @@ Remember that role assignments are inherited. If you assign a role at a subscrip
 Now that you understand the components of a role assignment, you can decide the appropriate values for your scenarios. Here are some general guidelines to consider:
 
 > [!div class="checklist"]
-> - Use the least permissive role that you can. If your pipeline is only going to deploy basic Bicep templates and won't manage role assignments, don't use the Owner role.
+> - Use the least permissive role that you can. If your pipeline is only going to deploy basic Bicep files and won't manage role assignments, don't use the Owner role.
 > - Use the narrowest scope that you can. Most pipelines only need to deploy resources to a resource group, so they shouldn't be given subscription-scoped role assignments.
 > - For many pipelines, a good default option for a role assignment is the Contributor role on the resource group scope.
 > - Consider everything your pipeline does, and everything it might do in the future. For example, you might consider creating a custom role definition for your website's deployment pipeline and only grant permissions for App Service and Application Insights. Next month, you might need to add an Azure Cosmos DB account to your Bicep file, but the custom role will block Azure Cosmos DB resources from being created. 
diff --git a/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/index.yml b/learn-pr/azure/authenticate-azure-deployment-pipeline-service-principals/index.yml
@@ -22,7 +22,7 @@ abstract: |
   - Configure the appropriate authorization for a service principal to deploy Azure resources.
 prerequisites: |
   You should be familiar with:
-  - Creating and deploying basic Bicep templates.
+  - Creating and deploying basic Bicep files.
   - Azure, including the Azure portal, subscriptions, resource groups, and resource definitions.
 
   To follow along with the exercises in the module, you'll need:
diff --git a/learn-pr/azure/authenticate-azure-deployment-workflow-workload-identities/includes/2-understand-workload-identities.md b/learn-pr/azure/authenticate-azure-deployment-workflow-workload-identities/includes/2-understand-workload-identities.md
@@ -12,7 +12,7 @@ All of these operations require permission because they access and modify your A
 - The ability to create and modify App Service plans and apps.
 - The ability to create and modify Application Insights instances.
 
-Until now, you've probably deployed your Bicep files yourself by using the Azure CLI or Azure PowerShell. When you use these tools, you normally use your own user account and authenticate by using your browser. This is called using your own _identity_. When you submit a deployment, Azure verifies that your identity has the necessary permissions to do what your Bicep template specifies.
+Until now, you've probably deployed your Bicep files yourself by using the Azure CLI or Azure PowerShell. When you use these tools, you normally use your own user account and authenticate by using your browser. This is called using your own _identity_. When you submit a deployment, Azure verifies that your identity has the necessary permissions to do what your Bicep file specifies.
 
 After you move to a GitHub Actions deployment workflow, you need to use a different type of identity, because the workflow runs deployments without your direct involvement.
 
diff --git a/learn-pr/azure/build-first-azd-template/includes/4-create-infrastructure.md b/learn-pr/azure/build-first-azd-template/includes/4-create-infrastructure.md
@@ -7,7 +7,7 @@ The Bicep or Terraform files for your template live in the `infra` folder. The `
 * `main.bicep` - Acts as the main entrypoint for Bicep execution and is used to define the resources that will be provisioned in Azure. The `main.bicep` file can also reference other Bicep modules (files) that allow you to extract out resource definitions into more granular, reusable files.
 * `abbreviations.json` - A JSON file that provides many helpful naming abbreviations. This file is loaded into the `main.bicep` file during execution and provides a set of consistent, logical naming prefixes for different Azure resources.
 * `main.parameters.json` - A JSON file that defines default values for important template parameters, such as the default Azure location or the environment name.
-* `core` - A subfolder that includes a variety of reusable Bicep templates you can use to generate common Azure resources by simply passing in configuration parameters.
+* `core` - A subfolder that includes a variety of reusable Bicep files you can use to generate common Azure resources by simply passing in configuration parameters.
 
 You can define and provision the required Azure resources for your app by updating the `main.bicep` file and creating custom Bicep files, or leveraging the templates in the `core` folder. `Main.bicep` generally orchestrates the execution of other Bicep modules by passing parameters between them. For this example, you'll create an additional minimal Bicep module to define the Azure App Service that will host your application.
 
diff --git a/learn-pr/azure/build-first-bicep-deployment-pipeline-using-azure-pipelines/includes/1-introduction.md b/learn-pr/azure/build-first-bicep-deployment-pipeline-using-azure-pipelines/includes/1-introduction.md
@@ -5,15 +5,15 @@ You can use Azure Pipelines to automate Bicep deployments. Azure Pipelines provi
 
 ## Example scenario
 
-Suppose you're responsible for deploying and configuring the Azure infrastructure to support a website at a toy company. You've built a Bicep template to deploy the website. Every time you need to reconfigure the website, you update your Bicep files and redeploy them from your computer. The website team asks for changes regularly, so the deployment process has become time-consuming. You want to find a way to automate the process so that you can focus on other tasks and initiatives.
+Suppose you're responsible for deploying and configuring the Azure infrastructure to support a website at a toy company. You've built a Bicep file to deploy the website. Every time you need to reconfigure the website, you update your Bicep files and redeploy them from your computer. The website team asks for changes regularly, so the deployment process has become time-consuming. You want to find a way to automate the process so that you can focus on other tasks and initiatives.
 
-You also want your colleagues to be able to make changes to the Bicep templates and deploy the templates themselves, but you need to make sure your colleagues follow the same process that you use. You decide to create a deployment pipeline that will run automatically every time the Bicep code is updated in your shared repository. The pipeline will deploy your Bicep files to Azure.
+You also want your colleagues to be able to make changes to the Bicep files and deploy the files themselves, but you need to make sure your colleagues follow the same process that you use. You decide to create a deployment pipeline that will run automatically every time the Bicep code is updated in your shared repository. The pipeline will deploy your Bicep files to Azure.
 
 :::image type="content" source="../media/1-workflow.png" alt-text="Diagram that shows a change to a Bicep file pushed to Azure Repos, and then a pipeline triggers deployment to Azure." border="false":::
 
 ## What will you learn?
 
-In this module, you'll learn how to automate the deployment of Bicep templates by using Azure Pipelines. You'll understand the benefits of using pipelines to deploy your code, and you'll build a basic pipeline that deploys a Bicep file. You'll also learn how to authorize your pipeline to deploy resources to your Azure environment and how to set when a pipeline runs.
+In this module, you'll learn how to automate the deployment of Bicep files by using Azure Pipelines. You'll understand the benefits of using pipelines to deploy your code, and you'll build a basic pipeline that deploys a Bicep file. You'll also learn how to authorize your pipeline to deploy resources to your Azure environment and how to set when a pipeline runs.
 
 ## What is the main goal?
 
diff --git a/learn-pr/azure/build-first-bicep-deployment-pipeline-using-azure-pipelines/includes/10-summary.md b/learn-pr/azure/build-first-bicep-deployment-pipeline-using-azure-pipelines/includes/10-summary.md
@@ -1,6 +1,6 @@
 Your toy company regularly updates its website, and it was becoming time consuming for you to manually deploy updated Bicep files. You also were the only person in your company who knew how to deploy the website infrastructure.
 
-In this module, you learned how to use Azure Pipelines to create an automated deployment process. You built a pipeline that automatically deploys your resources to Azure by using Bicep templates. You also learned how to trigger pipelines for every change that is made to your Bicep code, on a set schedule, or both. The process you successfully completed in the exercises can be scaled from a single person to an entire organization.
+In this module, you learned how to use Azure Pipelines to create an automated deployment process. You built a pipeline that automatically deploys your resources to Azure by using Bicep files. You also learned how to trigger pipelines for every change that is made to your Bicep code, on a set schedule, or both. The process you successfully completed in the exercises can be scaled from a single person to an entire organization.
 
 Thanks to your efforts, anyone on your website team can automatically deploy changes to your Azure environment, and they run through the same process for every change.
 
diff --git a/learn-pr/azure/build-first-bicep-deployment-pipeline-using-azure-pipelines/includes/2-understand-azure-pipelines.md b/learn-pr/azure/build-first-bicep-deployment-pipeline-using-azure-pipelines/includes/2-understand-azure-pipelines.md
@@ -15,7 +15,7 @@ Because a pipeline YAML file is a code file, the file is stored with your Bicep
 
 ## Agents and pools
 
-Until now, you've deployed your Bicep files from your local computer. After you write a Bicep template, you deploy it to Azure by using the Azure CLI or Azure PowerShell. These tools use your computer's resources to submit the template to Azure. They use your personal identity to authenticate you to Azure and to verify that you have the permissions to deploy the resources.
+Until now, you've deployed your Bicep files from your local computer. After you write a Bicep file, you deploy it to Azure by using the Azure CLI or Azure PowerShell. These tools use your computer's resources to submit the file to Azure. They use your personal identity to authenticate you to Azure and to verify that you have the permissions to deploy the resources.
 
 A pipeline also needs access to a computer so it can execute the deployment steps. Azure Pipelines uses a machine called an _agent_. An agent is a computer that's configured to run deployment steps for a pipeline. Each agent already has the Bicep and Azure tooling you used in earlier modules, so it can do the same things you do from your own computer. Instead of a human executing commands, the Azure Pipelines service instructs the agent to run the steps that you've defined in a YAML file.
 
diff --git a/learn-pr/azure/build-first-bicep-deployment-pipeline-using-github-actions/includes/1-introduction.md b/learn-pr/azure/build-first-bicep-deployment-pipeline-using-github-actions/includes/1-introduction.md
diff --git a/learn-pr/azure/build-first-bicep-deployment-pipeline-using-github-actions/includes/10-summary.md b/learn-pr/azure/build-first-bicep-deployment-pipeline-using-github-actions/includes/10-summary.md
diff --git a/learn-pr/azure/build-first-bicep-deployment-pipeline-using-github-actions/includes/2-understand-github-actions.md b/learn-pr/azure/build-first-bicep-deployment-pipeline-using-github-actions/includes/2-understand-github-actions.md
