Merge pull request #291508 from MicrosoftDocs/main

12/5/2024 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -4009,6 +4009,16 @@
       "source_path_from_root": "/articles/defender-for-iot/device-builders/overview-firmware-analysis.md",
       "redirect_url": "/azure/firmware-analysis/overview-firmware-analysis",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/managed-grafana/how-to-upgrade-grafana-10.md",
+      "redirect_url": "/azure/managed-grafana/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/managed-grafana/how-to-transition-domain.md",
+      "redirect_url": "/azure/managed-grafana/overview",
+      "redirect_document_id": false
     }
   ]
 }

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: ram-kakani
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 05/10/2024
+ms.date: 12/05/2024
 ms.author: ramakk
 ms.custom: references_regions
 ---
@@ -111,7 +111,8 @@ Configuring UDRs on the source VM subnets with the address prefix of delegated s
 > To access an Azure NetApp Files volume from an on-premises network via a VNet gateway (ExpressRoute or VPN) and firewall, configure the route table assigned to the VNet gateway to include the `/32` IPv4 address of the Azure NetApp Files volume listed and point to the firewall as the next hop. Using an aggregate address space that includes the Azure NetApp Files volume IP address will not forward the Azure NetApp Files traffic to the firewall. 
 
 >[!NOTE]
->If you want to configure a UDR route in the VM VNet, to control the routing of packets destined for a regionally VNet-peered Azure NetApp Files standard volume, the UDR prefix must be more specific or equal to the delegated subnet size of the Azure NetApp Files volume. If the UDR prefix is of size greater than the delegated subnet size, it will not be effective. 
+> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual alliance or firewall destined to an Azure NetApp Files standard volume from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Azure NetApp Files volume. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective. 
+> For example, if your delegated subnet is `x.x.x.x/24`, you must configured your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall. 
 
 ## Azure native environments
 

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

@@ -185,7 +185,7 @@ The following message shows an example for Bicep version.
   ```
 
 For the available methods & request/response bodies, see [`ICliJsonRpcProtocol.cs`](https://github.com/Azure/bicep/blob/main/src/Bicep.Cli/Rpc/ICliJsonRpcProtocol.cs).
-For an example establishing a JSONRPC connection and interacting with Bicep files programmatically using Node, see [`jsonrpc.test.ts`](https://github.com/Azure/bicep/blob/main/src/Bicep.Cli.E2eTests/src/jsonrpc.test.ts).
+For an example establishing a JSONRPC connection and interacting with Bicep files programmatically using Node, see [`jsonrpc.test.ts`](https://github.com/Azure/bicep/blob/main/src/Bicep.Cli.E2eTests/src/local/jsonrpc.test.ts).
 
 ### Usage for named pipe
 

articles/azure-resource-manager/management/move-support-resources.md

@@ -999,7 +999,7 @@ Moves between Resource groups and subscriptions are supported for APIs that use
 > | Resource type | Resource group | Subscription | Region move |
 > | ------------- | ----------- | ---------- | ----------- |
 > | accounts | **Yes** | **Yes** | No. [Learn more](/azure/azure-monitor/app/create-workspace-resource#how-do-i-move-an-application-insights-resource-to-a-new-region). |
-> | actiongroups | No | No | No |
+> | actiongroups | **Yes** | **Yes** | No |
 > | activitylogalerts | No | No | No |
 > | alertrules | **Yes** | **Yes** | No |
 > | autoscalesettings | **Yes** | **Yes** | No |

articles/azure-vmware/includes/create-private-cloud-azure-portal-steps.md

@@ -4,7 +4,7 @@ description: Steps to create an Azure VMware Solution private cloud using the Az
 ms.topic: include
 ms.service: azure-vmware
 ms.custom: devx-track-azurecli, engagement-fy23
-ms.date: 1/03/2024
+ms.date: 12/5/2024
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -51,7 +51,7 @@ You can create an Azure VMware Solution private cloud using the Azure portal or
 1. Verify the information entered, and if correct, select **Create**.  
 
    > [!NOTE]
-   > This step takes roughly 3-4 hours. Adding a single host in an existing or the same cluster takes between 30 - 45 minutes.
+   > This step takes an estimated 4+ hours. Adding a single host in an existing cluster takes an estimated 1 hour. If you are adding a new cluster with maximum nodes (16), it can take an estimated 4+ hours.
 
 1. Verify that the deployment was successful. Navigate to the resource group you created and select your private cloud.  You see the status of **Succeeded** when the deployment is finished. 
 

articles/communication-services/concepts/analytics/logs/voice-and-video-logs.md

@@ -107,7 +107,7 @@ For each endpoint within a call, a distinct call diagnostic log is created for o
 | `identifier` | The unique ID for the user. The identity can be an Azure Communication Services user, a Microsoft Entra user ID, a Teams object ID, or a Teams bot ID. You can use this ID to correlate user events across logs. |
 | `endpointId` | The unique ID that represents each endpoint connected to the call, where `endpointType` defines the endpoint type. When the value is `null`, the connected entity is the Communication Services server. `EndpointId` can persist for the same user across multiple calls (`correlationId`) for native clients but is unique for every call when the client is a web browser. |
 | `endpointType` | The value that describes the properties of each `endpointId` instance. It can contain  `"Server"`, `"VOIP"`, `"PSTN"`, `"BOT"`, `"Voicemail"`, `"Anonymous"`, or `"Unknown"`. |
-| `mediaType` | The string value that describes the type of media that's being transmitted between endpoints within each stream. Possible values include `"Audio"`, `"Video"`, `"VBSS"` (video-based screen sharing), and `"AppSharing"`. |
+| `mediaType` | The string value that describes the type of media that's being transmitted between endpoints within each stream. Possible values include `"Audio"`, `"Video"`, `"VBSS"` (screen sharing), and `"AppSharing"` (data channel).|
 | `streamId` | A nonunique integer that, together with `mediaType`, you can use to uniquely identify streams of the same `participantId` value. |
 | `transportType` | The string value that describes the network transport protocol for each `participantId` value. It can contain `"UDP"`, `"TCP"`, or `"Unrecognized"`. `"Unrecognized"` indicates that the system couldn't determine if the transport type was TCP or UDP. |
 | `roundTripTimeAvg` | The average time that it takes to get an IP packet from one endpoint to another within a `participantDuration` period. This network propagation delay is related to the physical distance between the two points, the speed of light, and any overhead that the various routers take in between. <br><br>The latency is measured as one-way time or round-trip time (RTT). Its value expressed in milliseconds. An RTT greater than 500 ms is negatively affecting the call quality. |

articles/firewall/management-nic.md

@@ -12,13 +12,13 @@ ms.author: victorh
 # Azure Firewall Management NIC
 
 > [!NOTE]
-> This feature was previously called Forced Tunneling. Originally, a Management NIC was required only for Forced Tunneling. However, upcoming Firewall features will also require a Management NIC, so it has been decoupled from Forced Tunneling. All relevant documentation has been updated to reflect this.
+> This feature was previously called Forced Tunneling. Originally, a Management NIC was required only for Forced Tunneling. However, certain upcoming Firewall features will also require a Management NIC, so it has been decoupled from Forced Tunneling. All relevant documentation has been updated to reflect this.
 
-An Azure Firewall Management NIC separates firewall management traffic from customer traffic. Upcoming Firewall features will also require a Management NIC. To support any of these capabilities, you must create an Azure Firewall with the Firewall Management NIC enabled or enable it on an existing Azure Firewall. This is a mandatory requirement to avoid service disruption.
+An Azure Firewall Management NIC separates firewall management traffic from customer traffic. Certain upcoming Firewall features will also require a Management NIC. To support any of these capabilities, you must create an Azure Firewall with the Firewall Management NIC enabled or enable it on an existing Azure Firewall to avoid service disruption.
 
 ## What happens when you enable the Management NIC
 
-If you enable a Management NIC, the firewall routes its management traffic via the AzureFirewallManagementSubnet (minimum subnet size /26) with its associated public IP address. You assign this public IP address for the firewall to manage traffic. It's used exclusively by the Azure platform and can't be used for any other purpose. All traffic required for firewall operational purposes is incorporated into the AzureFirewallManagementSubnet. 
+If you enable a Management NIC, the firewall routes its management traffic via the AzureFirewallManagementSubnet (minimum subnet size /26) with its associated public IP address. You assign this public IP address for the firewall to manage traffic. All traffic required for firewall operational purposes is incorporated into the AzureFirewallManagementSubnet. 
 
 By default, the service associates a system-provided route table to the Management subnet. The only route allowed on this subnet is a default route to the Internet and *Propagate gateway routes* must be disabled. Avoid associating customer route tables to the Management subnet, as this can cause service disruptions if configured incorrectly. If you do associate a route table, then ensure it has a default route to the Internet to avoid service disruptions.
 
@@ -91,33 +91,33 @@ Now when you view the firewall in the Azure portal, you see the assigned Managem
 If you prefer to deploy a new Azure Firewall instead of the Stop/Start method, make sure to include a Management Subnet and Management NIC as part of your configuration.
 
 **Important Note**
-* **Single Firewall per Virtual Network (VNET)**: Since two firewalls cannot exist within the same virtual network, it is recommended to delete the old firewall before starting the new deployment if you plan to reuse the same VNET.
-* **Pre-create Subnet**: Ensure the **AzureFirewallManagementSubnet** is created in advance to avoid deployment issues when using an existing VNET.
+* **Single Firewall per Virtual Network (VNET)**: Since two firewalls can't exist within the same virtual network, it's recommended to delete the old firewall before starting the new deployment if you plan to reuse the same virtual network.
+* **Pre-create Subnet**: Ensure the **AzureFirewallManagementSubnet** is created in advance to avoid deployment issues when using an existing virtual network.
 
 **Prerequisites**
 * Create the **AzureFirewallManagementSubnet**:
     * Minimum subnet size: /26
     * Example: 10.0.1.0/26
 
 **Deployment Steps**
-1. Go to **Create a Resource** in the Azure Portal.
+1. Go to **Create a Resource** in the Azure portal.
 1.	Search for **Firewall** and select **Create**.
-1.	On the Create a Firewall page, configure the following:
+1.	On the Create a Firewall page, configure the following settings:
     * **Subscription**: Select your subscription.
     * **Resource Group**: Select or create a new resource group.
     * **Name**: Enter a name for the firewall.
     * **Region**: Choose your region.
     * **Firewall SKU**: Select Basic, Standard, or Premium.
     * **Virtual Network**: Create a new virtual network or use an existing one.
-         * Address space: e.g., 10.0.0.0/16
-         * Subnet for AzureFirewallSubnet: e.g., 10.0.0.0/26
+         * Address space: for example, 10.0.0.0/16
+         * Subnet for AzureFirewallSubnet: for example, 10.0.0.0/26
     * **Public IP Address**: Add new Public IP
-         * Name: e.g., FW-PIP
+         * Name: for example, FW-PIP
 1.	Firewall Management NIC
     * Select **Enable Firewall Management NIC**
-         * Subnet for AzureFirewallManagementSubnet: e.g., 10.0.1.0/24
-         * Create Management public IP address: e.g., Mgmt-PIP
-1.	Select **Review + Create** to validate and deploy the firewall. This will take a few minutes to deploy. 
+         * Subnet for AzureFirewallManagementSubnet: for example, 10.0.1.0/24
+         * Create Management public IP address: for example, Mgmt-PIP
+1.	Select **Review + Create** to validate and deploy the firewall. This takes a few minutes to deploy. 
 
 
 ## Related content

articles/governance/machine-configuration/how-to/develop-custom-package/1-set-up-authoring-environment.md

@@ -24,7 +24,7 @@ Support for applying configurations through machine configuration is introduced
 
 Operating systems where the module can be installed:
 
-- Ubuntu 18
+- Ubuntu 18 or higher
 - Windows
 
 The module can be installed on a machine running PowerShell 7.x. Install the versions of PowerShell

articles/iot-hub-device-update/support.md

@@ -42,9 +42,6 @@ The systems listed in the following tables are supported by Microsoft, either ge
 | Ubuntu Server 22.04 | ![Ubuntu Server 22.04 + AMD64](./media/support/green-check.png) |  | ![Ubuntu Server 22.04 + ARM64](./media/support/green-check.png) |
 
 
-> [!NOTE]
-> [Standard support for Ubuntu 18.04 LTS ends on May 31st, 2023](https://ubuntu.com/blog/18-04-end-of-standard-support). Beginning June 2023, Ubuntu 18.04 LTS won't be a supported platform. Ubuntu 18.04 LTS Device Update packages are available until Nov 30th, 2023. If you take no action, Ubuntu 18.04 LTS based Device Update devices continue to work but ongoing security patches and bug fixes in the host packages for Ubuntu 18.04 won't be available after Nov 30th, 2023. To continue to receive support and security updates, we recommend that you update your host OS to a supported platform. 
-
 ## Releases and Support
 
 Device Update for IoT Hub release assets and release notes are available on the [Device Update Release](https://github.com/Azure/iot-hub-device-update/releases) page. Support for the APIs, PnP Models, and device update reference agents is covered in the table. 

articles/logic-apps/logic-apps-overview.md

@@ -98,6 +98,10 @@ To learn how other companies improved their agility and increased focus on their
 
 All these services help you connect and bring together disparate systems. Each service has their advantages and benefits, so combining their capabilities is the best way to quickly build a scalable, full-featured integration system. For more information, see [Choose between Azure Logic Apps, Azure Functions, Azure WebJobs, and Microsoft Power Automate](../azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md).
 
+## How does Azure Logic Apps differ from Azure Automation Runbooks?
+
+[Azure Automation Runbooks](/azure/automation/automation-runbook-types) provide a lightweight and cost-effective solution for straightforward remediations, such as restarting virtual machines. In contrast, Azure Logic Apps are ideal for workflows and orchestrations between multiple services, systems, apps, and data. including workloads that run custom code or require complex logic that uses control structures such as loops, branching, conditions, and more.
+
 ## How quickly can I ramp up my solutions with Azure Logic Apps?
 
 You can start small with your current systems and services, and then grow incrementally at your own pace. When you're ready, Azure Logic Apps helps you implement and scale up to more mature integration scenarios by providing the following capabilities and benefits.