Merge pull request #310214 from MicrosoftDocs/main

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

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

articles/azure-netapp-files/application-volume-group-add-volume-secondary.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 07/11/2025
+ms.date: 01/07/2026
 ms.author: anfdocs
 ms.custom:
   - build-2025
@@ -72,10 +72,10 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
     * **Availability option**:
         Select either **Availability zone** or **Proximity placement group**. 
         When selecting **Availability zone**, you must select the appropriate availability zone in the next field. 
-        * **Proximity placement group (PPG)**:  
-            Specifies that the data, log, and shared volumes are to be created close to the VMs.
         * **Availability Zone**: 
             This option lets you deploy the volumes in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
+        * **Proximity placement group (PPG)**:  
+            Specifies that the data, log, and shared volumes are to be created close to the VMs. Have at least one **deployed and running** HANA VM in the availability set with the assigned PPG. 
     * **Network features**: 
         Standard network features is the default, however you can still use Basic network features. 
         See [Configure network features for a volume](configure-network-features.md) and [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details.

articles/azure-netapp-files/application-volume-group-deploy-first-host.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 07/11/2025
+ms.date: 01/07/2026
 ms.author: anfdocs
 ms.custom:
   - build-2025
@@ -23,8 +23,8 @@ This article describes how to deploy the first SAP HANA host using Azure NetApp
 - Understand the [requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md). 
 
 - Application volume group for SAP HANA enables you to select Standard network features and availability zone volume placement without using volume pinning.
-    Alternately, adhere to the **[pinning recommendations](https://aka.ms/HANAPINNING)**. Have at least one HANA virtual machine (VM) in the availability set started. 
-
+    Alternately, adhere to the **[pinning recommendations](https://aka.ms/HANAPINNING)**, and have at least one **deployed and running** HANA VM in the availability set.
+  
 ## Steps 
 
 1. From your NetApp account, select **Application volume groups**, then **+Add Group**.
@@ -61,10 +61,10 @@ This article describes how to deploy the first SAP HANA host using Azure NetApp
 
         Select either **Availability zone** or **Proximity placement group**. 
         When selecting **Availability zone**, you must select the appropriate availability zone in the next field. 
-        * **Proximity placement group (PPG)**:  
-            Specifies that the data, log, and shared volumes are to be created close to the VMs.
         * **Availability Zone**: 
             This option lets you deploy the volumes in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
+        * **Proximity placement group (PPG)**:  
+            Specifies that the data, log, and shared volumes are to be created close to the VMs. Have at least one **deployed and running** HANA VM in the availability set with the assigned PPG. 
     * **Network features**: 
 
         Standard network features is the default, however you can still use Basic network features. 

articles/backup/azure-kubernetes-service-cluster-restore-using-cli.md

@@ -3,7 +3,7 @@ title: Restore Azure Kubernetes Service (AKS) using Azure CLI
 description: This article explains how to restore backed-up Azure Kubernetes Service (AKS) using Azure CLI.
 ms.topic: how-to
 ms.service: azure-backup
-ms.date: 01/30/2025
+ms.date: 04/14/2025
 ms.custom:
   - devx-track-azurecli
   - ignite-2023

articles/backup/backup-azure-backup-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: 'Answers to common questions about'
   ms.topic: faq
   ms.service: azure-backup
-  ms.date: 12/30/2025
+  ms.date: 01/07/2025
   author: AbhishekMallick-MS
   ms.author: v-mallicka
   ms.custom: engagement-fy24
@@ -117,8 +117,24 @@ sections:
           When GRS is enabled can we restore the VM on to the dedicated zone?
         answer: |
           No, we cannot restore on to the dedicated zone.
+      - question: |
+          Can I permanently delete the default Backup Policies in an Azure Recovery Services Vault?
+        answer: |
+          No, the default backup policies cannot be permanently deleted. Azure automatically recreates them to ensure baseline backup functionality. These policies are:
+          
+          - System-managed
+          - Non-deletable
+          - Non-deletable
+          - Used as fallback policies
 
-  - name: Backup vault
+          So even if you delete them through the portal, PowerShell, CLI, or REST API, they will always reappear.
+         
+          **Recommended approach:**
+          - Simply ignore the default policies.
+          - Create and use your own custom policies with your preferred naming standards.
+          - Ensure no backup items are associated with the default ones.
+          
+  - name: Backup Vault
     questions:
       - question: |
           Can I move a subscription that contains a Backup vault to a different tenant?

articles/communication-services/concepts/numbers/phone-number-management-for-australia.md

@@ -23,7 +23,7 @@ Use the below tables to find all the relevant information on number availability
 | Toll-Free                 | -                    | -                    | -                    | General Availability\* |
 | Local                     | -                    | -                    | General Availability | General Availability\* |
 | Mobile                    | General Availability\** | General Availability\**       | -                    | -                      |
-| Alphanumeric Sender ID\** | General Availability | -                    | -                    | -                      |
+| Alphanumeric Sender ID\** | -                    | -                    | -                    | -                      |
 
 \* Please refer to [Inbound calling capabilities page](../telephony/inbound-calling-capabilities.md) for details.
 
@@ -65,26 +65,6 @@ More details on eligible subscription types are as follows:
 | United Kingdom  |
 | United States  |
 
-## Azure subscription billing locations where Australia alphanumeric sender IDs are available
-| Country/Region |
-| :---------- |
-| Australia |
-| Austria |
-| Denmark |
-| France |
-| Germany |
-| India |
-| Ireland |
-| Italy |
-| Netherlands |
-| Poland |
-| Portugal |
-| Puerto Rico |
-| Spain |
-| Sweden |
-| Switzerland |
-| United Kingdom |
-| United States |
 
 [!INCLUDE [Azure Prepayment](../../includes/azure-prepayment.md)]
 
@@ -98,3 +78,4 @@ For more information about Azure Communication Services' telephony options, see
 
 - [Learn more about Telephony](../telephony/telephony-concept.md)
 - Get a Telephony capable [phone number](../../quickstarts/telephony/get-phone-number.md)
+

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

@@ -704,6 +704,16 @@
             "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
+        },
+        {
+            "source_path_from_root": "/articles/iot-operations/connect-to-cloud/howto-configure-wasm-graph-definitions.md",
+            "redirect_url": "/azure/iot-operations/develop-edge-apps/howto-configure-wasm-graph-definitions",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/iot-operations/connect-to-cloud/howto-configure-registry-endpoint.md",
+            "redirect_url": "/azure/iot-operations/develop-edge-apps/howto-configure-registry-endpoint",
+            "redirect_document_id": true
         }
     ]
 }