Merge pull request #292904 from MicrosoftDocs/main

Albertyang0 · web-flow · commit 4b51a0ea100d · 2025-01-10T10:15:08.000-08:00
1/10/2025 AM Publish
diff --git a/articles/active-directory-b2c/language-customization.md b/articles/active-directory-b2c/language-customization.md
@@ -466,7 +466,7 @@ Microsoft provides the `ui_locales` OIDC parameter to social logins. But some so
 
 ### Browser behavior
 
-Chrome and Firefox both request for their set language. If it's a supported language, it's displayed before the default. Microsoft Edge currently doesn't request a language and goes straight to the default language.
+Microsoft Edge, Chrome and Firefox request for their set language. If it's a supported language, it's displayed before the default.
 
 ## Supported languages
 
diff --git a/articles/active-directory-b2c/tutorial-create-user-flows.md b/articles/active-directory-b2c/tutorial-create-user-flows.md
@@ -221,7 +221,7 @@ Now, grant permissions to the API scope you exposed earlier in the *IdentityExpe
 1. Select the **APIs my organization uses** tab, then select the **IdentityExperienceFramework** application.
 1. Under **Permission**, select the **user_impersonation** scope that you defined earlier.
 1. Select **Add permissions**. As directed, wait a few minutes before proceeding to the next step.
-1. Select **Grant admin consent for *<your tenant name)>***.
+1. Select **Grant admin consent for *&lt;your tenant name>***.
 1. Select **Yes**.
 1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for the scope.
 
diff --git a/articles/active-directory-b2c/whats-new-docs.md b/articles/active-directory-b2c/whats-new-docs.md
@@ -1,7 +1,7 @@
 ---
 title: "What's new in Azure Active Directory business-to-customer (B2C)"
 description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
-ms.date: 12/02/2024
+ms.date: 01/10/2025
 ms.service: azure-active-directory
 ms.subservice: b2c
 ms.topic: whats-new
@@ -10,34 +10,31 @@ ms.author: kengaderdus
 author: kengaderdus
 manager: CelesteDG
 
-
 #Customer intent: As a developer using Azure Active Directory B2C, I want to stay updated on the latest documentation changes and new features, so that I can effectively use and implement the B2C service in my applications.
-
 ---
 
 # Azure Active Directory B2C: What's new
 
-Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
+Welcome to what's new in Azure Active Directory B2C documentation. This article lists new and significantly updated docs from the past three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
+
+## December 2024
+
+### Updated articles
+
+- [Tutorial: Configure Nok Nok S3 Authentication Suite with Azure AD B2C for FIDO passkey authentication](partner-nok-nok.md) - Updated scenarios
 
 ## November 2024
 
 ### Updated articles
 
-- [Azure Active Directory B2C: Region availability & data residency](data-residency.md) - Updated data residency location 
+- [Azure Active Directory B2C: Region availability & data residency](data-residency.md) - Updated data residency location
 
 ## October 2024
 
 ### Updated articles
 
-- [Secure APIs used for API connectors in Azure AD B2C](secure-rest-api.md) - ROPC flow updates
+- [Secure APIs used for API connectors in Azure AD B2C](secure-rest-api.md) - Flow updates
 - [Application types that can be used in Active Directory B2C](application-types.md) - Implicit grant flow updates
 - [Configure authentication in a sample single-page application by using Azure AD B2C](configure-authentication-sample-spa-app.md) - Implicit grant flow updates
 - [Single-page application sign-in using the OAuth 2.0 implicit flow in Azure Active Directory B2C](implicit-flow-single-page-application.md) - Implicit grant flow updates
-- [Register a single-page application in Azure Active Directory B2C](tutorial-register-spa.md) - Implicit grant flow updates
-
-## September 2024
-
-### Updated articles
-
-- [Developer notes for Azure Active Directory B2C](custom-policy-developer-notes.md) - Updated feature availability for China cloud
-
+- [Register a single-page application in Azure Active Directory B2C](tutorial-register-spa.md) - Implicit grant flow updates
diff --git a/articles/app-service/breadcrumb/toc.yml b/articles/app-service/breadcrumb/toc.yml
@@ -11,11 +11,17 @@ items:
     topicHref: /azure/app-service/index
   - name: App Service
     tocHref: /azure/developer/
-    topicHref: /azure/app-service/index
+    topicHref: /azure/app-service/index 
     items:
     - name: Web Apps
       tocHref: /entra/fundamentals/
       topicHref: /azure/app-service/index
     - name: Web Apps
       tocHref: /azure/developer/
+      topicHref: /azure/app-service/index
+    - name: Web Apps
+      tocHref: /azure/architecture/
+      topicHref: /azure/app-service/index
+    - name: Web Apps
+      tocHref: /azure/api-management/
       topicHref: /azure/app-service/index
diff --git a/articles/azure-vmware/includes/vmware-software-versions.md b/articles/azure-vmware/includes/vmware-software-versions.md
@@ -3,7 +3,7 @@ title: VMware solution software versions
 description: Supported VMware solution software versions for Azure VMware Solution.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 12/24/2024
+ms.date: 1/10/2025
 author: suzizuber
 ms.author: v-suzuber
 ms.custom: engagement-fy23
@@ -13,16 +13,16 @@ ms.custom: engagement-fy23
 
 The VMware solution software versions used in new deployments of Azure VMware Solution private clouds are:
 
-| Software                         |    Version   |
-| :---                             |     :---:    |
-| VMware vCenter Server            |    [8.0 U2d](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u2d-release-notes.html)   |
-| VMware ESXi                      |    [8.0 U2b](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u2b-release-notes.html)  |
-| VMware vSAN                      |    [8.0 U2](https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/release-notes/vmware-vsan-802-release-notes.html)   |
-| VMware vSAN on-disk format       |    [19](https://knowledge.broadcom.com/external/article?legacyId=2148493)   |
-| VMware vSAN storage architecture |    [OSA](https://blogs.vmware.com/cloud-foundation/2022/08/31/comparing-the-original-storage-architecture-to-the-vsan-8-express-storage-architecture/)   |
-| VMware NSX                       |    [!INCLUDE [nsxt-version](nsxt-version.md)]   |
-| VMware HCX                       |    [4.9.1](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-9/hcx-4-9-release-notes/Chunk701473140.html#Chunk701473140)   |
-| VMware Site Recovery Manager     |    [8.8.0.3](https://techdocs.broadcom.com/us/en/vmware-cis/live-recovery/site-recovery-manager/8-8/release-notes/vmware-site-recovery-manager-8803-release-notes.html)   |
-| VMware vSphere Replication       |    [8.8.0.3](https://techdocs.broadcom.com/us/en/vmware-cis/live-recovery/vsphere-replication/8-8/release-notes/vsphere-replication-8803-release-notes.html)   |
+| Software                         |    Version   |    Build number   |
+| :---                             |     :---:    |     :---:         |
+| VMware vCenter Server            |    [8.0 U2d](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-80u2d-release-notes.html)   | 23929136 |
+| VMware ESXi                      |    [8.0 U2b](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u2b-release-notes.html)  | 23305546 |
+| VMware vSAN                      |    [8.0 U2](https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/release-notes/vmware-vsan-802-release-notes.html)   | N/A |
+| VMware vSAN on-disk format       |    [19](https://knowledge.broadcom.com/external/article?legacyId=2148493)   | N/A |
+| VMware vSAN storage architecture |    [OSA](https://blogs.vmware.com/cloud-foundation/2022/08/31/comparing-the-original-storage-architecture-to-the-vsan-8-express-storage-architecture/)   | N/A |
+| VMware NSX                       |    [!INCLUDE [nsxt-version](nsxt-version.md)]   | 22224317 |
+| VMware HCX                       |    [4.9.1](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-9/hcx-4-9-release-notes/Chunk701473140.html#Chunk701473140)   | 23857539 |
+| VMware Site Recovery Manager     |    [8.8.0.3](https://techdocs.broadcom.com/us/en/vmware-cis/live-recovery/site-recovery-manager/8-8/release-notes/vmware-site-recovery-manager-8803-release-notes.html)   | 23263429 |
+| VMware vSphere Replication       |    [8.8.0.3](https://techdocs.broadcom.com/us/en/vmware-cis/live-recovery/vsphere-replication/8-8/release-notes/vsphere-replication-8803-release-notes.html)   | 23166649 |
 
 The current running software version is applied to new clusters added to an existing private cloud, if the vCenter Server version supports it.
diff --git a/articles/cdn/edgio-retirement-faq.md b/articles/cdn/edgio-retirement-faq.md
@@ -61,7 +61,7 @@ Important notes regarding these "best effort" automatic migrations to Azure Fron
 |-------------------|---------------------------------------------------------------------------------------------------------------------------|
 | Custom domain couldn't be migrated as domain validation could not be performed due to missing CNAME | [Manually perform domain validation](../frontdoor/standard-premium/how-to-add-custom-domain.md) |
 | Customer was using APEX domain | [Use Alias record on Azure DNS to use APEX domain](../frontdoor/front-door-how-to-onboard-apex-domain.md)|
-| Customer was using SAS token through rule engine to access their Azure Storage backend which has public access disabled | [Upgrade](../frontdoor/tier-upgrade.md) to Front Door Premium and use [private link](../frontdoor/standard-premium/how-to-enable-private-link-storage-account.md) |
+| Customer was using SAS token through rule engine to access their Azure Storage backend which has public access disabled | [Upgrade](../frontdoor/tier-upgrade.md) to Front Door Premium and use [private link](../frontdoor/standard-premium/how-to-enable-private-link-storage-account.md). If you are facing any errors in setting up private link, raise a support ticket. |
 | Customer was using geo-filtering rules which were not migrated | [Configure geo-filtering using WAF](../web-application-firewall/afds/waf-front-door-tutorial-geo-filtering.md)|
 
 ### What is the recap of the key dates?
diff --git a/articles/databox-online/azure-stack-edge-gpu-overview.md b/articles/databox-online/azure-stack-edge-gpu-overview.md
@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: overview
-ms.date: 10/09/2024
+ms.date: 01/10/2025
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Pro GPU is and how it works so I can use it to process and transform data before sending it to Azure.
 ---
diff --git a/articles/databox-online/azure-stack-edge-mini-r-overview.md b/articles/databox-online/azure-stack-edge-mini-r-overview.md
@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: overview
-ms.date: 10/09/2024
+ms.date: 01/10/2025
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Mini R is and how it works so I can use it to process and transform data before sending to Azure.
 ---
diff --git a/articles/databox-online/azure-stack-edge-pro-2-overview.md b/articles/databox-online/azure-stack-edge-pro-2-overview.md
@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: overview
-ms.date: 10/09/2024
+ms.date: 01/10/2025
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Pro 2 is and how it works so I can use it to process and transform data before sending to Azure.
 ---
diff --git a/articles/databox-online/azure-stack-edge-pro-r-overview.md b/articles/databox-online/azure-stack-edge-pro-r-overview.md
@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: overview
-ms.date: 10/09/2024
+ms.date: 01/10/2025
 ms.author: alkohli
 #Customer intent: As an IT admin, I need to understand what Azure Stack Edge Pro R is and how it works so I can use it to process and transform data before sending to Azure.
 ---
diff --git a/articles/firewall-manager/create-policy-powershell.md b/articles/firewall-manager/create-policy-powershell.md
@@ -4,7 +4,7 @@ description: In this quickstart, you learn how create and update an Azure Firewa
 services: firewall-manager
 author: vaboya
 ms.author: victorh
-ms.date: 08/16/2021
+ms.date: 01/10/2025
 ms.topic: quickstart
 ms.service: azure-firewall-manager
 ms.custom: mode-api, devx-track-azurepowershell
diff --git a/articles/firewall-manager/migrate-to-policy.md b/articles/firewall-manager/migrate-to-policy.md
@@ -5,7 +5,7 @@ author: vhorne
 ms.service: azure-firewall-manager
 services: firewall-manager
 ms.topic: how-to
-ms.date: 09/12/2022
+ms.date: 01/10/2025
 ms.author: victorh 
 ms.custom: devx-track-azurepowershell
 ---
diff --git a/articles/reliability/migrate-api-mgt.md b/articles/reliability/migrate-api-mgt.md
@@ -92,8 +92,6 @@ To migrate an existing location of your API Management instance to availability
 
 To migrate an existing location of your API Management instance to availability zones when the instance is currently injected in a virtual network and is already hosted on the `stv2` platform:
 
-1. Create a new subnet and optional public IP address in the location to migrate to availability zones. Detailed requirements are in the [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
-
 1. In the Azure portal, go to your API Management instance.
 
 1. On the **Deployment + infrastructure** menu, select **Locations**.
@@ -104,7 +102,7 @@ To migrate an existing location of your API Management instance to availability
 
 1. In the **Availability zones** box, select one or more zones. The number of units that you selected must be distributed evenly across the availability zones. For example, if you selected three units, select three zones so that each zone hosts one unit.
 
-1. In the **Public IP Address** box, optionally select the new public IP address in the location.
+1. In the **Public IP Address** box, optionally select a public IP address in the location.
 
 1. Select **Apply**, and then select **Save**.
 
diff --git a/articles/reliability/reliability-postgresql-flexible-server.md b/articles/reliability/reliability-postgresql-flexible-server.md
@@ -2,10 +2,10 @@
 title: Reliability and high availability in PostgreSQL - Flexible Server
 titleSuffix: Azure Database for PostgreSQL - Flexible Server
 description: Find out about reliability and high availability in Azure Database for PostgreSQL - Flexible Server
-author: sunilagarwal
-ms.author: anaharris
-ms.reviewer: maghan, anaharris
-ms.date: 11/5/2024
+author: gkasar
+ms.author: gkasar
+ms.reviewer: maghan, gbowerman
+ms.date: 01/10/2025
 ms.service: azure-database-postgresql
 ms.topic: conceptual
 ms.custom:
@@ -30,7 +30,7 @@ Azure Database for PostgreSQL - Flexible Server offers high availability support
 
 Azure Database for PostgreSQL - Flexible Server supports both [zone-redundant and zonal models](availability-zones-service-support.md) for high availability configurations. Both high availability configurations enable automatic failover capability with zero data loss during both planned and unplanned events.
 
-- **Zone-redundant**. Zone redundant high availability deploys a standby replica in a different zone with automatic failover capability. Zone redundancy provides the highest level of availability, but requires you to configure application redundancy across zones. For that reason, choose zone redundancy when you want protection from availability zone level failures and when latency across the availability zones is acceptable.
+- **Zone-redundant**. Zone redundant high availability deploys a standby replica in a different zone with automatic failover capability. Zone redundancy provides the highest level of availability, but requires you to configure application redundancy across zones. For that reason, choose zone redundancy when you want protection from availability zone level failures and when latency across the availability zones is acceptable. While there can be some latency impact on writes and commits due to synchronous replication, it doesn't affect read queries. This impact is very specific to your workloads, the SKU type you select, and the region.
 
     You can choose the region and the availability zones for both primary and standby servers. The standby replica server is provisioned in the chosen availability zone in the same region with a similar compute, storage, and network configuration as the primary server. Data files and transaction log files (write-ahead logs, a.k.a WAL) are stored on locally redundant storage (LRS) within each availability zone, automatically storing **three** data copies. A zone-redundant configuration provides physical isolation of the entire stack between primary and standby servers.
 
diff --git a/articles/service-bus-messaging/how-to-use-java-message-service-20.md b/articles/service-bus-messaging/how-to-use-java-message-service-20.md
@@ -2,7 +2,7 @@
 title: Use Java Message Service 2.0 API with Azure Service Bus Premium
 description: How to use the Java Message Service (JMS) with Azure Service Bus
 ms.topic: article
-ms.date: 12/16/2022
+ms.date: 01/10/2024
 ms.custom: devx-track-extended-java
 ---
 
@@ -11,7 +11,11 @@ ms.custom: devx-track-extended-java
 This article explains how to use the popular **Java Message Service (JMS) 2.0** API to interact with Azure Service Bus over the Advanced Message Queueing Protocol (AMQP) 1.0 protocol.
 
 > [!NOTE]
-> Support for Java Message Service (JMS) 2.0 API is only available in the **premium tier**.>
+> Support for JMS 2.0 API is available only in the premium tier and when you use the **azure-servicebus-jms** library. If you use JMS libraries other than **azure-servicebus-jms** (for example, latest **qpid-jms-client**) against a premium namespace, you observe the JMS 1.1 behavior. The azure-servicebus-jms library doesn't create a vendor lock of any kind as it still takes a dependency on qpid-jms-client. All APIs that work on qpid-jms-client work on azure-servicebus-jms library as well. 
+>
+>  The azure-servicebus-jms is also an [open-source library](https://github.com/azure/azure-servicebus-jms). The azure-servicebus-jms library was mainly created so that the Service Bus service can distinguish between customers needing the JMS 1.1 behavior (backwards compatibility) versus the JMS 2.0 behavior when working against a premium namespace. The azure-servicebus-jms library also provides some necessary defaults such as prefetch policy values, reconnect policies, Microsoft Entra ID, Managed Identity support, support for Auto Delete on Idle for entities out of the box.
+> 
+> The following path to the azure-servicebus-jms package is the latest version of the library that is based on the Jakarta Messaging specification (Jakarta.* APIs): Maven Central: [com.azure:azure-servicebus-jms](https://central.sonatype.com/artifact/com.azure/azure-servicebus-jms). And, the following path to the azure-servicebus-jms is the latest version of library before the Jakarta Messaging specification  (javax.* APIs): Maven Central: [com.microsoft.azure:azure-servicebus-jms](https://central.sonatype.com/artifact/com.microsoft.azure/azure-servicebus-jms/versions).
 
 ## Prerequisites
 
diff --git a/articles/storage/common/storage-use-azcopy-v10.md b/articles/storage/common/storage-use-azcopy-v10.md
@@ -303,15 +303,15 @@ wget -O azcopy_v10.tar.gz https://aka.ms/downloadazcopy-v10-linux && tar -xf azc
 ```
 **Windows PowerShell** 
 ```PowerShell
-Invoke-WebRequest -Uri 'https://azcopyvnext.azureedge.net/release20220315/azcopy_windows_amd64_10.14.1.zip' -OutFile 'azcopyv10.zip'
+Invoke-WebRequest -Uri <URL from the previous command> -OutFile 'azcopyv10.zip'
 Expand-archive -Path '.\azcopyv10.zip' -Destinationpath '.\'
 $AzCopy = (Get-ChildItem -path '.\' -Recurse -File -Filter 'azcopy.exe').FullName
 # Invoke AzCopy 
 & $AzCopy
 ```
 **PowerShell 6.1+**
 ```PowerShell
-Invoke-WebRequest -Uri 'https://azcopyvnext.azureedge.net/release20220315/azcopy_windows_amd64_10.14.1.zip' -OutFile 'azcopyv10.zip'
+Invoke-WebRequest -Uri <URL from the previous command> -OutFile 'azcopyv10.zip'
 $AzCopy = (Expand-archive -Path '.\azcopyv10.zip' -Destinationpath '.\' -PassThru | where-object {$_.Name -eq 'azcopy.exe'}).FullName
 # Invoke AzCopy
 & $AzCopy
diff --git a/includes/azure-stack-edge-use-case-parameters.md b/includes/azure-stack-edge-use-case-parameters.md
