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

Author: gitName

articles/app-service/app-service-undelete.md

@@ -8,7 +8,7 @@ ms.topic: article
 ms.custom: devx-track-azurepowershell
 ---
 
-# Restore deleted App Service app Using PowerShell
+# Restore Deleted App Service App Using PowerShell
 
 If you happened to accidentally delete your app in Azure App Service, you can restore it using the commands from the [Az PowerShell module](/powershell/azure/).
 

articles/app-service/toc.yml

@@ -403,11 +403,11 @@
       href: deploy-intelligent-apps.md
 - name: WordPress
   items:
+    - name: WordPress overview
+      href: overview-wordpress.md
     - name: WordPress architecture
       displayName: WordPress on App Service architecture
       href: /azure/architecture/example-scenario/infrastructure/wordpress-app-service
-    - name: WordPress overview
-      href: overview-wordpress.md
     - name: Deploy WordPress
       displayName: Create a WordPress site
       href: quickstart-wordpress.md

articles/app-service/tutorial-python-postgresql-app.md

@@ -142,22 +142,6 @@ python manage.py runserver
 
 ## 1. Create App Service and PostgreSQL
 
-
-### [Flask](#tab/flask)
-
-```bash
-git clone https://github.com/Azure-Samples/msdocs-flask-postgresql-sample-app.git
-```
-
-### [Django](#tab/django)
-
-```bash
-git clone https://github.com/Azure-Samples/msdocs-django-postgresql-sample-app.git
-```
-
------
-
-
 In this step, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service and Azure Database for PostgreSQL. For the creation process, you'll specify:
 
 * The **Name** for the web app. It's the name used as part of the DNS name for your webapp in the form of `https://<app-name>.azurewebsites.net`.

articles/azure-cache-for-redis/cache-how-to-premium-vnet.md

@@ -28,6 +28,8 @@ ms.date: 12/12/2024
   - potential data loss
   - failure of management operations like scaling
   - intermittent or complete SSL/TLS failures
+  - failure to apply updates, including important security and reliability improvements
+    
   - in the most severe scenarios, loss of availability
 - VNet injected caches are only available for Premium-tier Azure Cache for Redis, not other tiers.
 - When using a VNet injected cache, you must change your VNet to cache dependencies such as Certificate Revocation Lists/Public Key Instructure, Azure Key Vault, Azure Storage, Azure Monitor, and more.

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

@@ -16,7 +16,7 @@ This article describes how to use Bicep extensions.
 The syntax for importing Bicep extensions is:
 
 ```bicep
-extionsion <extension-name>
+extension <extension-name>
 ```
 
 The syntax for importing Bicep extensions, which require configuration is:
@@ -35,4 +35,4 @@ For examples, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md)
 - To learn about Bicep functions, see [Bicep functions](./bicep-functions.md).
 - To learn how to use the Bicep Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 - To go through a Kubernetes extension tutorial, see [Quickstart: Deploy Azure applications to Azure Kubernetes Services by using the Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
-- To learn Microsoft Graph extension, see [Microsoft Graph extension](https://aka.ms/graphbicep).
+- To learn Microsoft Graph extension, see [Microsoft Graph extension](https://aka.ms/graphbicep).

articles/azure-vmware/toc.yml

@@ -53,8 +53,6 @@ items:
     href: enable-sql-azure-hybrid-benefit.md
   - name: Save costs with a reserved instance
     href: reserved-instance.md
-  - name: Azure hybrid benefit for Windows Server, SQL Server, and Linux subscriptions
-    href: sql-server-hybrid-benefit.md
   - name: VMware Cloud Foundations (VCF) license portability on Azure VMware Solution
     href: vmware-cloud-foundations-license-portability.md
 - name: Architecture

articles/batch/pool-endpoint-configuration.md

@@ -2,7 +2,7 @@
 title: Configure node endpoints in Azure Batch pool
 description: How to configure node endpoints such as access to SSH or RDP ports on compute nodes in an Azure Batch pool.
 ms.topic: how-to
-ms.date: 11/08/2024
+ms.date: 12/16/2024
 ---
 
 # Configure remote access to compute nodes in an Azure Batch pool
@@ -12,10 +12,11 @@ externally to a compute node in a Batch pool. For example, a user can connect by
 compute node in a Windows pool. Similarly, by default, a user can connect by Secure Shell (SSH) on port 22 to a compute
 node in a Linux pool.
 
-> [!TIP]
-> As of API version `2024-07-01`, Batch no longer automatically maps common remote access ports for SSH and RDP.
-> If you wish to allow remote access to your Batch compute nodes with pools created with API version `2024-07-01` or later,
-> then you must manually configure the pool endpoint configuration to enable such access.
+> [!NOTE]
+> As of API version `2024-07-01` (and all pools created after **30 November 2025** regardless of API version), Batch no
+> longer automatically maps common remote access ports for SSH and RDP. If you wish to allow remote access to your Batch
+> compute nodes with pools created with API version `2024-07-01` or later (and after 30 November 2025), then you must
+> manually configure the pool endpoint configuration to enable such access.
 
 In your environment, you might need to enable, restrict, or disable external access settings or any other ports you wish
 on the Batch pool. You can modify these settings by using the Batch APIs to set the
@@ -167,4 +168,4 @@ class AzureBatch(object):
 ## Next steps
 
 - Learn about the [Batch service workflow and primary resources](batch-service-workflow-features.md) such as pools, nodes, jobs, and tasks.
-- For more information about NSG rules in Azure, see [Filter network traffic with network security groups](../virtual-network/network-security-groups-overview.md).
+- Learn more about NSG rules in Azure with [Filtering network traffic with network security groups](../virtual-network/network-security-groups-overview.md).

articles/business-continuity-center/index.yml

@@ -13,7 +13,7 @@ metadata:
   ms.topic: landing-page
   author: AbhishekMallick-MS
   ms.author: v-abhmallick
-  ms.date: 11/19/2024
+  ms.date: 12/16/2024
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
 landingContent:
@@ -31,10 +31,34 @@ landingContent:
           - text: Azure Business Continuity center support matrix
             url: business-continuity-center-support-matrix.md
 
+  # Card (optional)
+  - title: Manage data protection
+    linkLists:
+      - linkListType: quickstart
+        links:
+          - text: Understand the protection estate
+            url: quick-understand-protection-estate.md
+      - linkListType: tutorial
+        links:
+          - text: Configure protection for data sources
+            url: tutorial-configure-protection-datasource.md
+          - text: Recover deleted items
+            url: tutorial-recover-deleted-item.md
+          - text: Configure and view reports
+            url: tutorial-reporting-for-data-insights.md
+
   # Card (optional)
   - title: Monitor protection
     linkLists:
       - linkListType: how-to-guide
         links:
           - text: Monitor protection summary
             url: tutorial-monitor-protection-summary.md
+
+  # Card (optional)
+  - title: Azure Business Continuity Center Copilot (preview)
+    linkLists:
+      - linkListType: tutorial
+        links:
+          - text: Manage BCDR estate (preview)
+            url: tutorial-manage-data-using-copilot.md

articles/cloud-services/cloud-services-troubleshoot-common-issues-which-cause-roles-recycle.md

@@ -24,7 +24,7 @@ If a role in your application relies on any assembly that isn't part of the .NET
 
 Before you build and package your application, verify the following statements are true:
 
-* If using Visual studio, make sure the **Copy Local** property is set to **True** for each referenced assembly in your project that isn't part of the Azure SDK or the .NET Framework.
+* If using Visual Studio, make sure the **Copy Local** property is set to **True** for each referenced assembly in your project that isn't part of the Azure SDK or the .NET Framework.
 * Make sure the web.config file doesn't reference any unused assemblies in the compilation element.
 * The **Build Action** of every .cshtml file is set to **Content**. This setting ensures that the files appear correctly in the package and enables other referenced files to appear in the package.
 

articles/communication-services/concepts/voice-video-calling/pre-call-diagnostics.md

@@ -11,7 +11,7 @@ ms.topic: conceptual
 ms.service: azure-communication-services
 ---
 
-# Pre-call diagnostic
+# Pre-call diagnostic overview
 
 [!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]