Merge pull request #280619 from MicrosoftDocs/main

7/11/2024 AM Publish

Author: Taojunshen

articles/api-management/self-hosted-gateway-settings-reference.md

@@ -120,7 +120,7 @@ This guidance helps you provide the required information to define how to authen
 
 | Name  | Description | Required | Default | Availability |
 | ------------- | ------------- | ------------- | ----| ----|
-| Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls13 | Indication whether or not SSL 3.0 is allowed towards the backend. Similar to [managing protocol ciphers in managed gateway](api-management-howto-manage-protocols-ciphers.md). | No | `true` | v2.0+ |
+| Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls13 | Indication whether or not TLS 1.3 is allowed towards the backend. Similar to [managing protocol ciphers in managed gateway](api-management-howto-manage-protocols-ciphers.md). | No | `true` | v2.0+ |
 | Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls12 | Indication whether or not TLS 1.2 is allowed towards the backend. Similar to [managing protocol ciphers in managed gateway](api-management-howto-manage-protocols-ciphers.md). | No | `true` | v2.0+ |
 | Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls11 | Indication whether or not TLS 1.1 is allowed towards the backend. Similar to [managing protocol ciphers in managed gateway](api-management-howto-manage-protocols-ciphers.md). | No | `false` | v2.0+ |
 | Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls10 | Indication whether or not TLS 1.0 is allowed towards the backend. Similar to [managing protocol ciphers in managed gateway](api-management-howto-manage-protocols-ciphers.md). | No | `false` | v2.0+ |

articles/application-gateway/understanding-pricing.md

@@ -48,6 +48,7 @@ The parameter with the highest utilization among these three parameters is used
 
 #### Capacity Unit related to Instance Count
 <h4 id="instance-count"></h4>
+
 You can also pre-provision resources by specifying the **Instance Count**. Each instance guarantees a minimum of 10 capacity units in terms of processing capability. The same instance could potentially support more than 10 capacity units for different traffic patterns depending upon the capacity unit parameters.
 
 Manually defined scale and limits set for autoscaling (minimum or maximum) are set in terms of instance count. The manually set scale for instance count and the minimum instance count in autoscale config reserves 10 capacity units/instance. These reserved capacity units are billed as long as the application gateway is active regardless of the actual resource consumption. If actual consumption crosses the 10 capacity units/instance threshold, additional capacity units are billed under the variable component.

articles/azure-arc/system-center-virtual-machine-manager/overview.md

@@ -1,7 +1,7 @@
 ---
 title:  Overview of the Azure Connected System Center Virtual Machine Manager 
 description: This article provides a detailed overview of the Azure Arc-enabled System Center Virtual Machine Manager.
-ms.date: 06/27/2024
+ms.date: 07/11/2024
 ms.topic: overview
 ms.services: azure-arc
 ms.subservice: azure-arc-scvmm
@@ -86,23 +86,6 @@ Azure Arc-enabled SCVMM is currently supported in the following regions:
 - Southeast Asia
 - Australia East
 
-### Resource bridge networking requirements
-
-The following firewall URL exceptions are needed for the Azure Arc resource bridge VM:
-
-[!INCLUDE [network-requirements](../resource-bridge/includes/network-requirements.md)]
-
-In addition, SCVMM requires the following exception:
-
-| **Service** | **Port** | **URL** | **Direction** | **Notes**|
-| --- | --- | --- | --- | --- |
-| SCVMM Management Server | 443 | URL of the SCVMM management server. | Appliance VM IP and control plane endpoint need outbound connection. | Used by the SCVMM server to communicate with the Appliance VM and the control plane. |
-| WinRM | WinRM Port numbers (Default: 5985 and 5986). | URL of the WinRM service. | IPs in the IP Pool used by the Appliance VM and control plane need connection with the VMM server. | Used by the SCVMM server to communicate with the Appliance VM. |
-
-[!INCLUDE [network-requirement-principles](../includes/network-requirement-principles.md)]
-
-For a complete list of network requirements for Azure Arc features and Azure Arc-enabled services, see [Azure Arc network requirements (Consolidated)](../network-requirements-consolidated.md).
-
 ## Data Residency
 
 Azure Arc-enabled SCVMM doesn't store/process customer data outside the region the customer deploys the service instance in.

articles/azure-arc/system-center-virtual-machine-manager/support-matrix-for-system-center-virtual-machine-manager.md

@@ -7,7 +7,7 @@ ms.subservice: azure-arc-scvmm
 author: PriskeyJeronika-MS
 ms.author: v-gjeronika
 manager: jsuri
-ms.date: 07/10/2024
+ms.date: 07/11/2024
 keywords: "VMM, Arc, Azure"
 
 # Customer intent: As a VI admin, I want to understand the support matrix for System Center Virtual Machine Manager.
@@ -55,13 +55,9 @@ In addition, SCVMM requires the following exception:
 | SCVMM Management Server | 443 | URL of the SCVMM management server. | Appliance VM IP and control plane endpoint need outbound connection. | Used by the SCVMM server to communicate with the Appliance VM and the control plane. |
 | WinRM | WinRM Port numbers (Default: 5985 and 5986). | URL of the WinRM service. | IPs in the IP Pool used by the Appliance VM and control plane need connection with the VMM server. | Used by the SCVMM server to communicate with the Appliance VM. |
 
-Generally, connectivity requirements include these principles: 
+[!INCLUDE [network-requirement-principles](../includes/network-requirement-principles.md)]
 
-- All connections are TCP unless otherwise specified. 
-- All HTTP connections use HTTPS and SSL/TLS with officially signed and verifiable certificates. 
-- All connections are outbound unless otherwise specified. 
-
-To use a proxy, verify that the agents and the machine performing the onboarding process meet the network requirements in this article. For a complete list of network requirements for Azure Arc features and Azure Arc-enabled services, see [Azure Arc network requirements (Consolidated)](../network-requirements-consolidated.md).
+For a complete list of network requirements for Azure Arc features and Azure Arc-enabled services, see [Azure Arc network requirements (Consolidated)](../network-requirements-consolidated.md).
 
 ### Azure role/permission requirements
 

articles/azure-arc/system-center-virtual-machine-manager/toc.yml

@@ -4,6 +4,8 @@
   items:
   - name: About Azure Arc-enabled SCVMM
     href: overview.md
+  - name: Plan for deployment
+    href: support-matrix-for-system-center-virtual-machine-manager.md
   - name: Switch to the new version
     href: switch-to-the-new-version-scvmm.md
 - name: Quickstarts
@@ -22,8 +24,6 @@
   items:
   - name: Deploy
     items:
-    - name: Plan for deployment
-      href: support-matrix-for-system-center-virtual-machine-manager.md
     - name: Enable SCVMM inventory resources in Azure
       href: enable-scvmm-inventory-resources.md
     - name: Enable virtual hardware and VM CRUD capabilities in an SCVMM machine with Arc agent installed

articles/azure-monitor/alerts/action-groups.md

@@ -351,7 +351,7 @@ When an email address is rate limited, a notification is sent to communicate tha
 When you use Azure Resource Manager for email notifications, you can send email to the members of a subscription's role. Email is sent to Microsoft Entra ID **user** or **group** members of the role. This includes support for roles assigned through Azure Lighthouse.
 
 > [!NOTE]
-> Action Groups only supports emailing the following roles: Owner, Contirbutor, Reader, Monitoring Contributor, Monitoring Reader.
+> Action Groups only supports emailing the following roles: Owner, Contributor, Reader, Monitoring Contributor, Monitoring Reader.
 
 If your primary email doesn't receive notifications, configure the email address for the Email Azure Resource Manager role:
 

articles/azure-monitor/containers/media/prometheus-remote-write-managed-identity/data-collection-rule-add-role-assignment.png

@@ -5,7 +5,7 @@ author: johndowns
 ms.author: jodowns
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/23/2023
+ms.date: 07/11/2024
 ---
 # Best practices for Bicep
 
@@ -53,8 +53,12 @@ For more information about Bicep variables, see [Variables in Bicep](variables.m
 
 * It's a good practice to use template expressions to create resource names, like in this example:
 
-  :::code language="bicep" source="~/azure-docs-bicep-samples/samples/best-practices/resource-name-expressions.bicep" highlight="3":::
-
+  ```bicep
+  param shortAppName string = 'toy'
+  param shortEnvironmentName string = 'prod'
+  param appServiceAppName string = '${shortAppName}-${shortEnvironmentName}-${uniqueString(resourceGroup().id)}'
+  ```
+  
   Using template expressions to create resource names gives you several benefits:
 
   * Strings generated by `uniqueString()` aren't meaningful. It's helpful to use a template expression to create a name that includes meaningful information, such as a short descriptor of the project or environment name, as well as a random component to make the name more likely to be unique.
@@ -68,13 +72,13 @@ For more information about Bicep variables, see [Variables in Bicep](variables.m
 * Avoid using `name` in a symbolic name. The symbolic name represents the resource, not the resource's name. For example, instead of the following syntax:
 
   ```bicep
-  resource cosmosDBAccountName 'Microsoft.DocumentDB/databaseAccounts@2023-04-15' = {
+  resource cosmosDBAccountName 'Microsoft.DocumentDB/databaseAccounts@2023-11-15' = {
   ```
 
   Use:
 
   ```bicep
-  resource cosmosDBAccount 'Microsoft.DocumentDB/databaseAccounts@2023-04-15' = {
+  resource cosmosDBAccount 'Microsoft.DocumentDB/databaseAccounts@2023-11-15' = {
   ```
 
 * Avoid distinguishing variables and parameters by the use of suffixes.

articles/azure-resource-manager/bicep/best-practices.md

@@ -3,7 +3,7 @@ title: Bicep CLI commands and overview
 description: Describes the commands that you can use in the Bicep CLI. These commands include building Azure Resource Manager templates from Bicep.
 ms.topic: reference
 ms.custom: devx-track-azurecli, devx-track-bicep, devx-track-arm-template
-ms.date: 01/02/2024
+ms.date: 07/11/2024
 ---
 
 # Bicep CLI commands
@@ -172,6 +172,16 @@ The command returns an array of available versions.
 
 ```azurecli
 [
+  "v0.28.1",
+  "v0.27.1",
+  "v0.26.170",
+  "v0.26.54",
+  "v0.25.53",
+  "v0.25.3",
+  "v0.24.24",
+  "v0.23.1",
+  "v0.22.6",
+  "v0.21.1",
   "v0.20.4",
   "v0.19.5",
   "v0.18.4",
@@ -191,17 +201,7 @@ The command returns an array of available versions.
   "v0.9.1",
   "v0.8.9",
   "v0.8.2",
-  "v0.7.4",
-  "v0.6.18",
-  "v0.6.11",
-  "v0.6.1",
-  "v0.5.6",
-  "v0.4.1318",
-  "v0.4.1272",
-  "v0.4.1124",
-  "v0.4.1008",
-  "v0.4.613",
-  "v0.4.451"
+  "v0.7.4"
 ]
 ```
 

articles/azure-resource-manager/bicep/bicep-cli.md

@@ -3,7 +3,7 @@ title: Bicep extensibility Kubernetes provider
 description: Learn how to Bicep Kubernetes provider  to deploy .NET applications to Azure Kubernetes Service clusters.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-dotnet
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Bicep extensibility Kubernetes provider (Preview)
@@ -14,7 +14,7 @@ The Kubernetes provider allows you to create Kubernetes resources directly with
 > Kubernetes provider is not currently supported for private clusters:
 > 
 > ```bicep
-> resource AKS 'Microsoft.ContainerService/managedClusters@2023-01-02-preview' = {
+> resource AKS 'Microsoft.ContainerService/managedClusters@2024-02-01' = {
 >  ...
 >  properties: {
 >   apiServerAccessProfile: {
@@ -61,7 +61,7 @@ import '[email protected]' with {
 The following sample shows how to pass `kubeConfig` value from a parent Bicep file:
 
 ```bicep
-resource aks 'Microsoft.ContainerService/managedClusters@2022-05-02-preview' existing = {
+resource aks 'Microsoft.ContainerService/managedClusters@2024-02-01' existing = {
   name: 'demoAKSCluster'
 }