Merge pull request #246590 from mumian/0728-freshness-01

ARM content freshness - 5

Author: v-regandowner

articles/azure-resource-manager/bicep/patterns-shared-variable-file.md

@@ -5,7 +5,7 @@ author: johndowns
 ms.author: jodowns
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 07/01/2022
+ms.date: 07/28/2023
 ---
 # Shared variable file pattern
 
@@ -39,7 +39,7 @@ When you define your resource names, use string interpolation to concatenate the
 
 ## Example 2: Network security group rules
 
-Suppose you have multiple Bicep file that define their own network security groups (NSG). You have a common set of security rules that must be applied to each NSG, and then you have application-specific rules that must be added.
+Suppose you have multiple Bicep files that define their own network security groups (NSG). You have a common set of security rules that must be applied to each NSG, and then you have application-specific rules that must be added.
 
 Define a JSON file that includes the common security rules that apply across your company:
 

articles/azure-resource-manager/bicep/scenarios-monitoring.md

@@ -1,17 +1,16 @@
 ---
 title: Create monitoring resources by using Bicep
 description: Describes how to create monitoring resources by using Bicep.
-author: willvelida
-ms.author: willvelida
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 07/01/2022
+ms.date: 07/28/2023
 ---
+
 # Create monitoring resources by using Bicep
 
 Azure has a comprehensive suite of tools that can monitor your applications and services. You can programmatically create your monitoring resources using Bicep to automate the creation of rules, diagnostic settings, and alerts when provisioning your Azure infrastructure.
 
-Bringing your monitoring configuration into your Bicep code might seem unusual, considering that there are tools available inside the Azure portal to set up alert rules, diagnostic settings and dashboards. 
+Bringing your monitoring configuration into your Bicep code might seem unusual, considering that there are tools available inside the Azure portal to set up alert rules, diagnostic settings and dashboards.
 
 However, alerts and diagnostic settings are essentially the same as your other infrastructure resources. By including them in your Bicep code, you can deploy and test your alerting resources as you would for other Azure resources.
 
@@ -27,7 +26,7 @@ Diagnostic settings enable you to configure Azure Monitor to export your logs an
 
 When creating [diagnostic settings](../../azure-monitor/essentials/diagnostic-settings.md) in Bicep, remember that this resource is an [extension resource](scope-extension-resources.md), which means it's applied to another resource. You can create diagnostic settings in Bicep by using the resource type [Microsoft.Insights/diagnosticSettings](/azure/templates/microsoft.insights/diagnosticsettings?tabs=bicep).
 
-When creating diagnostic settings in Bicep, you need to apply the scope of the diagnostic setting. The diagnostic setting can be applied at the management, subscription, or resource group level. [Use the scope property on this resource to set the scope for this resource](../../azure-resource-manager/bicep/scope-extension-resources.md). 
+When creating diagnostic settings in Bicep, you need to apply the scope of the diagnostic setting. The diagnostic setting can be applied at the management, subscription, or resource group level. [Use the scope property on this resource to set the scope for this resource](../../azure-resource-manager/bicep/scope-extension-resources.md).
 
 Consider the following example:
 
@@ -87,7 +86,7 @@ Metric alerts notify you when one of your metrics crosses a defined threshold. Y
 
 The [Azure activity log](../../azure-monitor/essentials/activity-log.md) is a platform log in Azure that provides insights into events at the subscription level. This includes information such as when a resource in Azure is modified.
 
-Activity log alerts are alerts that are activated when a new activity log event occurs that matches the conditions that are specified in the alert. 
+Activity log alerts are alerts that are activated when a new activity log event occurs that matches the conditions that are specified in the alert.
 
 You can use the `scope` property within the type [Microsoft.Insights/activityLogAlerts](/azure/templates/microsoft.insights/activitylogalerts?tabs=bicep) to create activity log alerts on a specific resource or a list of resources using the resource IDs as a prefix.
 
@@ -120,11 +119,11 @@ For more information about creating dashboards with code, see [Programmatically
 
 ## Autoscale rules
 
-To create an autoscaling setting, you define these using the resource type [Microsoft.Insights/autoscaleSettings](/azure/templates/microsoft.insights/autoscalesettings?tabs=bicep). 
+To create an autoscaling setting, you define these using the resource type [Microsoft.Insights/autoscaleSettings](/azure/templates/microsoft.insights/autoscalesettings?tabs=bicep).
 
 To target the resource that you want to apply the autoscaling setting to, you need to provide the target resource identifier of the resource that the setting should be added to.
 
-In this example, a *scale out* condition for the App Service plan based on the average CPU percentage over a 10 minute time period. If the App Service plan exceeds 70% average CPU consumption over 10 minutes, the autoscale engine scales out the plan by adding one instance. 
+In this example, a *scale out* condition for the App Service plan based on the average CPU percentage over a 10 minute time period. If the App Service plan exceeds 70% average CPU consumption over 10 minutes, the autoscale engine scales out the plan by adding one instance.
 
 ::: code language="bicep" source="~/azure-docs-bicep-samples/samples/scenarios-monitoring/autoscaling-rules.bicep" :::
 

articles/azure-resource-manager/index.yml

@@ -13,7 +13,7 @@ metadata:
   ms.collection: collection
   author: tfitzmac
   ms.author: tomfitz
-  ms.date: 12/08/2021
+  ms.date: 07/28/2023
 
 # highlightedContent section (optional)
 # Maximum of 8 items

articles/azure-resource-manager/templates/template-tutorial-create-first-template.md

@@ -117,7 +117,7 @@ az account set --subscription SubscriptionName
 
 ## Create resource group
 
-When you deploy a template, you can specify a resource group to contain the resources. Before running the deployment command, create the resource group with either the Bash Azure CLI or Azure PowerShell. 
+When you deploy a template, you can specify a resource group to contain the resources. Before running the deployment command, create the resource group with either the Bash Azure CLI or Azure PowerShell.
 
 > [!NOTE]
 > Samples for the Azure CLI are written for the bash shell. To run this sample in Windows PowerShell or the Command Prompt, you may need to remove the back slashes and write the command as one line such as:

articles/container-registry/container-registry-get-started-bicep.md

@@ -6,7 +6,8 @@ author: mumian
 ms.author: jgao
 ms.date: 10/11/2022
 ms.topic: quickstart
-ms.service: azure-resource-manager
+ms.service: container-registry
+tags: azure-resource-manager, bicep
 ms.custom: mode-api, devx-track-bicep
 ---
 
@@ -22,7 +23,7 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
 
 ## Review the Bicep file
 
-Use Visual studio code or your favorite editor to create a file with the following content and name it **main.bicep**:
+Use Visual Studio Code or your favorite editor to create a file with the following content and name it **main.bicep**:
 
 ```bicep
 @minLength(5)

articles/container-registry/container-registry-get-started-geo-replication-template.md

@@ -7,6 +7,7 @@ ms.author: tejaswikolli
 ms.date: 10/11/2022
 ms.topic: quickstart
 ms.service: container-registry
+tags: azure-resource-manager
 ms.custom: subject-armqs, mode-arm, devx-track-arm-template
 ---
 
@@ -52,7 +53,7 @@ More Azure Container Registry template samples can be found in the [quickstart t
     * **Region**: select a location for the resource group. Example: **Central US**.
     * **Acr Name**: accept the generated name for the registry, or enter a name. It must be globally unique.
     * **Acr Admin User Enabled**: accept the default value.
-    * **Location**: accept the generated location for the registry's home replica, or enter a location such as **Central US**. 
+    * **Location**: accept the generated location for the registry's home replica, or enter a location such as **Central US**.
     * **Acr Sku**: accept the default value.
     * **Acr Replica Location**: enter a location for the registry replica, using the region's short name. It must be different from the home registry location. Example: **westeurope**.
 

articles/private-5g-core/deploy-private-mobile-network-with-site-arm-template.md

@@ -2,10 +2,11 @@
 title: Deploy a private mobile network and site - ARM template
 titleSuffix: Azure Private 5G Core
 description: Learn how to deploy a private mobile network and site using an Azure Resource Manager template (ARM template).
-services: azure-resource-manager 
+services: azure-resource-manager
 author: djrmetaswitch
 ms.author: drichards
-ms.service: azure-resource-manager
+ms.service: private-5g-core
+tags: azure-resource-manager
 ms.topic: quickstart
 ms.custom: subject-armqs, devx-track-arm-template
 ms.date: 03/23/2022
@@ -62,7 +63,7 @@ The following Azure resources are defined in the template.
 
 1. Select or enter the following values, using the information you retrieved in [Prerequisites](#prerequisites).
 
-    
+
     |Field  |Value  |
     |---------|---------|
     |**Subscription**     | Select the Azure subscription you want to use to create your private mobile network.        |
@@ -85,11 +86,11 @@ The following Azure resources are defined in the template.
     |**User Plane Data Interface Name**  | Enter the virtual network name on port 6 on your Azure Stack Edge Pro device corresponding to the user plane interface on the data network. For 5G, this interface is the N6 interface; for 4G, it's the SGi interface. |
     |**User Equipment Address Pool Prefix**  | Enter the network address of the subnet from which dynamic IP addresses must be allocated to User Equipment (UEs) in CIDR notation. You can omit this if you don't want to support dynamic IP address allocation. |
     |**User Equipment Static Address Pool Prefix**  | Enter the network address of the subnet from which static IP addresses must be allocated to User Equipment (UEs) in CIDR notation. You can omit this if you don't want to support static IP address allocation. |
-    |**Data Network Name**  | Enter the name of the data network. |    
+    |**Data Network Name**  | Enter the name of the data network. |
     |**Core Network Technology**  | Enter *5GC* for 5G, or *EPC* for 4G. |
     |**Napt Enabled** | Set this field depending on whether Network Address and Port Translation (NAPT) should be enabled for the data network.|
     | **Dns Addresses** | Enter the DNS server addresses. You should only omit this if you don't need the UEs to perform DNS resolution, or if all UEs in the network will use their own locally configured DNS servers. |
-    |**Custom Location** | Enter the resource ID of the custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site.|    
+    |**Custom Location** | Enter the resource ID of the custom location that targets the Azure Kubernetes Service on Azure Stack HCI (AKS-HCI) cluster on the Azure Stack Edge Pro device in the site.|
 
 2. Select **Review + create**.
 3. Azure will now validate the configuration values you've entered. You should see a message indicating that your values have passed validation.
@@ -113,9 +114,9 @@ The following Azure resources are defined in the template.
     - A **Packet Core Control Plane** resource representing the control plane function of the packet core instance in the site.
     - A **Packet Core Data Plane** resource representing the data plane function of the packet core instance in the site.
     - An **Attached Data Network** resource representing the site's view of the data network.
-    - A **Service** resource representing the default service. 
+    - A **Service** resource representing the default service.
     - A **SIM Policy** resource representing the allow-all SIM policy.
-    - A **SIM Group** resource (if you provisioned any SIMs). 
+    - A **SIM Group** resource (if you provisioned any SIMs).
 
     :::image type="content" source="media/create-full-private-5g-core-deployment-arm-template/full-deployment-resource-group.png" alt-text="Screenshot of the Azure portal showing a resource group containing the resources for a full Azure Private 5G Core deployment." lightbox="media/create-full-private-5g-core-deployment-arm-template/full-deployment-resource-group.png":::
 

articles/synapse-analytics/sql-data-warehouse/quickstart-arm-template.md

@@ -3,7 +3,9 @@ title: Create a dedicated SQL pool (formerly SQL DW) by using Azure Resource Man
 description: Learn how to create an Azure Synapse Analytics SQL pool by using Azure Resource Manager template.
 services: azure-resource-manager
 author: WilliamDAssafMSFT
-ms.service: azure-resource-manager
+ms.service: synapse-analytics
+ms.subservice: sql-dw
+tags: azure-resource-manager
 ms.topic: quickstart
 ms.author: wiassaf
 ms.date: 06/09/2020
@@ -37,7 +39,7 @@ The template defines one resource:
 ## Deploy the template
 
 1. Select the following image to sign in to Azure and open the template. This template creates a dedicated SQL pool (formerly SQL DW).
-   
+
    [![Deploy to Azure](../../media/template-deployments/deploy-to-azure.svg)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.sql%2Fsql-data-warehouse-transparent-encryption-create%2Fazuredeploy.json)
 
 1. Enter or update the following values:
@@ -49,7 +51,7 @@ The template defines one resource:
    * **SQL Administrator login**: Enter the administrator username for the SQL Server.
    * **SQL Administrator password**: Enter the administrator password for the SQL Server.
    * **Data Warehouse Name**: Enter a dedicated SQL pool name.
-   * **Transparent Data Encryption**: Accept the default, enabled. 
+   * **Transparent Data Encryption**: Accept the default, enabled.
    * **Service Level Objective**: Accept the default, DW400c.
    * **Location**: Accept the default location of the resource group.
    * **Review and Create**: Select.
@@ -64,7 +66,7 @@ You can either use the Azure portal to check the deployed resources, or use Azur
 ```azurecli-interactive
 echo "Enter the resource group where your dedicated SQL pool (formerly SQL DW) exists:" &&
 read resourcegroupName &&
-az resource list --resource-group $resourcegroupName 
+az resource list --resource-group $resourcegroupName
 ```
 
 # [PowerShell](#tab/PowerShell)

articles/synapse-analytics/sql-data-warehouse/quickstart-bicep.md

@@ -3,7 +3,9 @@ title: Create an Azure Synapse Analytics dedicated SQL pool (formerly SQL DW) us
 description: Learn how to create an Azure Synapse Analytics SQL pool using Bicep.
 services: azure-resource-manager
 author: rayoef
-ms.service: azure-resource-manager
+ms.service: synapse-analytics
+ms.subservice: sql-dw
+tags: azure-resource-manager, bicep
 ms.topic: quickstart
 ms.author: rayoflores
 ms.date: 05/20/2022