Merge pull request #310160 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-06 12:00 UTC

Author: learn-build-service-prod[bot]

articles/application-gateway/application-gateway-backend-health-troubleshooting.md

@@ -108,10 +108,11 @@ To increase the timeout value, follow these steps:
 **Resolution:**
 
 1. Verify that the FQDN entered in the backend pool is correct and that it's a public domain, then try to resolve it from your local machine.
-1. If you can resolve the IP address, there might be something wrong with the DNS configuration in the virtual network.
-1. Check whether the virtual network is configured with a custom DNS server. If it is, check the DNS server about why it can't resolve to the IP address of the specified FQDN.
-1. If you're using Azure default DNS, verify with your domain name registrar that proper A record or CNAME record mapping is complete.
-1. If the domain is private or internal, try to resolve it from a VM in the same virtual network. If you can resolve it, restart Application Gateway and check again. To restart Application Gateway, you need to [stop](/powershell/module/az.network/stop-azapplicationgateway) and [start](/powershell/module/az.network/start-azapplicationgateway) by using the PowerShell commands described in these linked resources.
+2. If you can resolve the IP address, there might be something wrong with the DNS configuration in the virtual network.
+3. Check whether the virtual network is configured with a custom DNS server. If it is, check the DNS server about why it can't resolve to the IP address of the specified FQDN.
+4. If you're using Azure default DNS, verify with your domain name registrar that proper A record or CNAME record mapping is complete.
+5. If the domain is private or internal, try to resolve it from a VM in the same virtual network. If you cannnot resolve it, restart Application Gateway and check again. To restart Application Gateway, you need to [stop](/powershell/module/az.network/stop-azapplicationgateway) and [start](/powershell/module/az.network/start-azapplicationgateway) by using the PowerShell commands described in these linked resources.
+6. If you're using short names (single-label domain names like `server1` instead of a fully-qualified domain name `server1.contoso.com`), verify that your DNS server can resolve the short name. Azure's built-in DNS (168.63.129.16) only resolves short names for resources within the same virtual network. For on-premises short names, use a custom DNS server configured with the appropriate search domains.
 
 ### TCP connect error
 

articles/application-gateway/application-gateway-components.md

@@ -130,7 +130,7 @@ A backend pool routes request to backend servers, which serve the request. Backe
 - Virtual machine scale sets
 - Public IP addresses
 - Internal IP addresses
-- FQDN
+- FQDN (fully qualified domain names) or short names (single-label domain names), provided your DNS server can resolve them
 - Multitenant backends (such as App Service)
 
 Application Gateway backend pool members aren't tied to an availability set. An application gateway can communicate with instances outside of the virtual network that it's in. As a result, the members of the backend pools can be across clusters, across datacenters, or outside Azure, as long as there's IP connectivity.

articles/azure-vmware/native-create-azure-vmware-virtual-network-private-cloud.md

@@ -40,17 +40,17 @@ Before you begin, these items are required to create an Azure VMware Solution Ge
 
 3. In the **Search services and marketplace** text box, type **Azure VMware Solution** and select it from the search results.
 
-4. On the **Azure VMware Solution** window, select **Create**. The following is the information needed to deploy the private cloud from your planning phase.
- 
+1. On the **Azure VMware Solution** window, select **Create**. The following is the information needed to deploy the private cloud from your planning phase.
+
    | Field                       | Value                                                                                                           |
    |-----------------------------|-----------------------------------------------------------------------------------------------------------------|
    | **Subscription**            | Select the subscription you plan to use for the deployment. All resources in an Azure subscription are billed together. |
    | **Resource group**          | Select the resource group for your private cloud. An Azure resource group is a logical container into which Azure resources are deployed and managed. Alternatively, you can create a new resource group for your private cloud. |
    | **Resource name**           | Provide the name of your Azure VMware Solution private cloud.                                                   |
    | **Location**                | Select a location, such as (US) East US 2. It's the region you defined during the planning phase.               |
    |**Size of host**            | Select the AV64 SKU.                                                                                            |
-   |**Availability zone**       | Select which availability zone you want your private cloud deployed in.                                         |
-   |**Number of hosts**         | Number of hosts allocated for the private cloud cluster. The default value is 3, which you can increase or decrease after deployment. If these nodes aren't listed as available, contact support to request a quota increase. You can also select the link labeled If you need more hosts, request a quota increase in the Azure portal. |
+   |**Availability zone _(Optional)_**| Select the Availability Zone where you want your private cloud deployed.  If no Availability Zone is selected, the private cloud will use the default placement. This is used to place workloads closer to on-premises environments or other Azure services to meet latency and data-proximity requirements, or to support disaster recovery and high-availability strategies by deploying across multiple zones.|
+   |**Number of hosts**         | Number of hosts allocated for the private cloud cluster. The default value is 3, which you can increase after deployment or decrease if you have 4 or more nodes deployed. If these nodes aren't listed as available, contact support to request a quota increase. You can also select the link labeled If you need more hosts, request a quota increase in the Azure portal. |
    |**Virtual Network**         | Azure Virtual Network with a minimum network address space of a /22 or 4 /24s. This can be a new or existing Virtual Network. The /22 or 4 /24s provided in your Virtual Network can be the same address space as the CIDR block you are planning to for your private cloud as long as the address space is not in use.|
    |**Address block for private cloud** | Provide an IP address block for the private cloud. The CIDR represents the private cloud management network and is used for the cluster management services, such as vCenter Server and NSX-T Manager. Use /22 address space, for example, 10.175.0.0/22. The address should be unique and not overlap with other Azure Virtual Networks and with on-premises networks that are in use. |
    |**DNS Forward Lookup**      | Input on your DNS Forward Lookup Zone. Either Private or Public. If no option is selected, the default is Public. This can be changed after your private cloud is created. |
@@ -62,8 +62,8 @@ Before you begin, these items are required to create an Azure VMware Solution Ge
 
 6. 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.
 
-6. 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.
-    
+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.
+
 7. Connect to vCenter Server and NSX Manager using the VMware credentials shown in your Private Cloud. For more information, see [Access an Azure VMware Solution private cloud](tutorial-access-private-cloud.md). 
 
 ## Next steps

articles/azure-vmware/native-introduction.md

@@ -43,7 +43,7 @@ With the Azure VMware Solution Gen 2 private clouds offering, you get the follow
 
 ### Other features and capabilities unlocked 
 - Ability to select Private DNS resolution for your private cloud, enabling businesses to communicate across Azure and on-premises environments without being exposed to the internal.  
-- Ability to select which availability zone to deploy your private cloud in to minimize latency to on-premises environments. 
+- Ability to select which availability zone to deploy your private cloud in to minimize latency to on-premises environments. Availability zones are typically specified when a customer wants their private cloud to be geographically closest to their on-premises data center. If availability zone selection is not required, no zone should be specified.
 
 ## Supported SKU type
 

articles/backup/azure-kubernetes-service-cluster-backup-support-matrix.md

@@ -2,7 +2,7 @@
 title: Azure Kubernetes Service (AKS) backup support matrix
 description: This article provides a summary of support settings and limitations of Azure Kubernetes Service (AKS) backup.
 ms.topic: reference
-ms.date: 06/10/2025
+ms.date: 01/06/2026
 ms.custom:
   - references_regions
   - ignite-2023
@@ -118,11 +118,11 @@ China East 2, China East 3, China North 2, China North 3, US GOV Arizona, US GOV
 
 - Currently, backup instances with <= 100 disks attached as persistent volume are supported. Backup and restore operations might fail if number of disks are higher than the limit. 
 
-- Only Azure Disks with public access enabled from all networks are eligible to be moved to the Vault Tier; if there are disks with network access apart from public access, tiering operation fails. 
-
+- Only Azure Disks that have public network access enabled, AAD (Data Access) authentication disabled, and Disk Encryption Set (DES) disabled are eligible to be moved to the Vault tier. If a disk has restricted network access, AAD authentication enabled, or DES enabled, the tiering operation will fail.
+  
 - *Disaster Recovery* feature is only available between Azure Paired Regions (if backup is configured in a Geo Redundant Backup vault with Cross Region Restore enabled on them). The backup data is only available in an Azure paired region. For example, if you have an AKS cluster in East US that is backed up in a Geo Redundant Backup vault with Cross Region Restore enabled on them, the backup data is also available in West US for restore.
 
-- In the Vault Tier, only one scheduled recovery point is created per day, providing a Recovery Point Objective (RPO) of 24 hours in the primary region. In the secondary region, replication of this recovery point can take up to 12 additional hours, resulting in an effective RPO of up to 36 hours.
+- In the Vault Tier, only one scheduled recovery point is created per day, providing a Recovery Point Objective (RPO) of upto 24 hours in the primary region. In the secondary region, replication of this recovery point can take up to 12 additional hours, resulting in an effective RPO of up to 36 hours.
 
 - When a backup is created in the Operational Tier and becomes eligible for Vault Tier, it may take up to four hours for the tiering process to begin.
 

articles/backup/backup-reports-email.md

@@ -2,7 +2,7 @@
 title: Email Azure Backup Reports
 description: Create automated tasks to receive periodic reports via email
 ms.topic: how-to
-ms.date: 12/10/2025
+ms.date: 12/30/2025
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-mallicka
@@ -183,5 +183,15 @@ You can also directly update the ARM template, which is used for deploying the l
 
 ---
 
+## Pricing for Email Reports
+
+Email reports are free. However, you incur charges for the Log Analytics workspace and Logic Apps that you use to configure and deliver email notifications. These charges apply as per the respective pricing models.
+
+The following examples illustrate the cost estimation for using Email Reports:
+
+- **Cost of actions**: Cost of the action type  (varies by the report you configure for email) x Count of actions × 30 days (a month).
+- **Cost of standard connectors**: Cost of connector x Count of connectors x 30 days (a month).
+- **Cost of data retention** (calculation for 7 days): 7 days × data volume per run in MB (determine the volume by running the workflow once and noting emitted storage metrics) × storage cost for each unit × 30 days (a month).
+
 ## Next steps
 [Learn more about Backup Reports](./configure-reports.md)

articles/backup/restore-afs.md

@@ -34,7 +34,7 @@ You can use this restore option to restore the complete File Share in the origin
 
 To restore the complete File Share, follow these steps:
 
-1. In the [Azure portal](https://portal.azure.com/), go to **Business Continuity Center** > **Protection inventory** > **Protected items**, and then select **Recover**.
+1. In the [Azure portal](https://portal.azure.com/), go to **Resiliency** > **Protection inventory** > **Protected items**, and then select **Recover**.
 1. On the **Recover** pane, select the **Azure Files (Azure Storage)** as the **Datasource type**, and then click **Select** under **Protected item**.
 
    The **Select restore point** context pane opens that lists the restore points available for the selected File Share. 
@@ -78,7 +78,7 @@ You can use this restore option to restore individual files or folders in the or
 
 To restore individual files or folders, follow these steps:
 
-1. Go to **Business Continuity Center**, and then select **Protected inventory** > **Protected items** from the menu, with the datasource type selected as **Azure Storage (Azure Files)**.
+1. Go to **Resiliency**, and then select **Protected inventory** > **Protected items** from the menu, with the datasource type selected as **Azure Storage (Azure Files)**.
 1. Select the File Share for which you want to do an item-level recovery.
 
    The *backup item* menu appears with a **File Recovery** option.
@@ -152,7 +152,7 @@ After you trigger the restore operation, the backup service creates a job for tr
 
 You can also monitor restore progress from the Recovery Services vault:
 
-1. Go to **Business Continuity Center** and select **Monitoring + Reporting** > **Jobs** from the menu.
+1. Go to **Resiliency**. and select **Monitoring + Reporting** > **Jobs** from the menu.
 1. On the **Jobs** pane, filter the jobs for the required solution and datasource type.
 
  >[!NOTE]

articles/data-factory/connector-file-system.md

@@ -5,7 +5,7 @@ description: Learn how to copy data from file system to supported sink data stor
 author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
-ms.date: 09/25/2024
+ms.date: 01/06/2026
 ms.author: jianleishen
 ms.custom:
   - synapse
@@ -34,7 +34,7 @@ This file system connector is supported for the following capabilities:
 Specifically, this file system connector supports:
 
 - Copying files from/to network file share. To use a Linux file share, install [Samba](https://www.samba.org/) on your Linux server.
-- Copying files using **Windows** authentication.
+- Copying files using **Basic** authentication.
 - Copying files as-is or parsing/generating files with the [supported file formats and compression codecs](supported-file-formats-and-compression-codecs.md).
 
 ## Prerequisites

articles/iot-operations/.openpublishing.redirection.iot-operations.json

@@ -699,6 +699,11 @@
             "source_path_from_root": "/articles/iot-operations/connect-to-cloud/howto-wasm-onnx-inference.md",
             "redirect_url": "/azure/iot-operations/develop-edge-apps/howto-wasm-onnx-inference",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/iot-operations/develop-edge-apps/overview-iot-operations-sdks.md",
+            "redirect_url": "/azure/iot-operations/develop-edge-apps/overview-iot-operations-development",
+            "redirect_document_id": true
         }
     ]
 }