Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into erpublicpeering

Author: duongau

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/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.

articles/oracle/oracle-db/oracle-database-regions.md

@@ -37,7 +37,6 @@ The following table lists Azure regions and corresponding OCI regions that suppo
 | France Central       |France central (Paris) | ✓   | ✓ |
 | Germany West Central |Germany Central (Frankfurt) |  ✓  | ✓ |
 | UK South             | UK South (London)   | ✓   | ✓    |
-| UK West              | UK West (Cardiff)   | ✓   | ✓    |
 | Italy North          | Italy North (Milan)   | ✓   |     |
 
 ## North America (NA)
@@ -56,6 +55,7 @@ The following table lists Azure regions and corresponding OCI regions that offer
 | Azure region   | OCI region  | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure |
 |----------------|--------------------------|-------------------|-------------------|
 | West US | US West (San Jose)  | ✓  |          ✓  |
+| UK West | UK West (Cardiff)   | ✓   | ✓    |
 
 > [!NOTE]
 > To provision Oracle Database@Azure resources in a supported region, your tenancy must be subscribed to the target region. Learn how to [manage regions](https://docs.oracle.com/iaas/Content/Identity/regions/managingregions.htm#Managing_Regions) and [subscribe to an infrastructure region](https://docs.oracle.com/iaas/Content/Identity/regions/To_subscribe_to_an_infrastructure_region.htm#subscribe).