Merge branch 'main' into release-hv4-amd-launch

Author: v-alje

.openpublishing.redirection.json

@@ -29356,12 +29356,12 @@
         },
         {
             "source_path_from_root": "/articles/availability-zones/az-overview.md",
-            "redirect_url": "/azure/reliablity/availability-zones-overview.md",
+            "redirect_url": "/azure/reliability/availability-zones-overview",
             "redirect_document_id": false
         },
         {
-            "source_path_from_root": "/articles/availability-zones/index.md",
-            "redirect_url": "/azure/reliablity/index.md",
+            "source_path_from_root": "/articles/availability-zones/index.yml",
+            "redirect_url": "/azure/reliability/index",
             "redirect_document_id": false
         },
         {

articles/active-directory/azuread-dev/azure-ad-endpoint-comparison.md

@@ -9,9 +9,9 @@ ms.service: active-directory
 ms.subservice: azuread-dev
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 07/17/2020
+ms.date: 11/09/2022
 ms.author: ryanwi
-ms.reviewer: marsma, ludwignick
+ms.reviewer: ludwignick
 ms.custom: aaddev
 ROBOTS: NOINDEX
 ---

articles/active-directory/develop/howto-authenticate-service-principal-powershell.md

@@ -10,7 +10,7 @@ ms.subservice: develop
 ms.custom: aaddev, devx-track-azurepowershell
 ms.topic: how-to
 ms.tgt_pltfrm: multiple
-ms.date: 10/11/2021
+ms.date: 11/09/2022
 ms.author: ryanwi
 ms.reviewer: tomfitz
 ---

articles/active-directory/develop/publisher-verification-overview.md

@@ -8,10 +8,10 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 06/01/2021
+ms.date: 11/09/2022
 ms.author: ryanwi
 ms.custom: aaddev
-ms.reviewer: ardhanap, jesakowi
+ms.reviewer: ardhanap, brianokoyo, jesakowi
 ---
 
 # Publisher verification
@@ -60,7 +60,7 @@ App developers must meet a few requirements to complete the publisher verificati
 
 - The domain of the email address that's used during MPN account verification must either match the publisher domain that's set for the app or be a DNS-verified [custom domain](../fundamentals/add-custom-domain.md) that's added to the Azure AD tenant.
 
-- The user who initiates verification must be authorized to make changes both to the app registration in Azure AD and to the MPN account in Partner Center.
+- The user who initiates verification must be authorized to make changes both to the app registration in Azure AD and to the MPN account in Partner Center.  The user who initiates the verification must have one of the required roles in both Azure AD and Partner Center.
 
   - In Azure AD, this user must be a member of one of the following [roles](../roles/permissions-reference.md): Application Admin, Cloud Application Admin, or Global Admin.
 

articles/active-directory/develop/registration-config-how-to.md

@@ -10,7 +10,7 @@ ms.subservice: develop
 ms.custom: aaddev 
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 09/27/2021
+ms.date: 11/09/2022
 ms.author: ryanwi
 ROBOTS: NOINDEX
 ---

articles/active-directory/develop/scenario-spa-call-api.md

@@ -2,15 +2,15 @@
 title: Build single-page app calling a web API
 description: Learn how to build a single-page application that calls a web API
 services: active-directory
-author: rwike77
+author: OwenRichards1
 manager: CelesteDG
 
 ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
 ms.date: 09/27/2021
-ms.author: ryanwi
+ms.author: owenrichards
 ms.custom: aaddev
 #Customer intent: As an application developer, I want to know how to write a single-page application by using the Microsoft identity platform.
 ---

articles/active-directory/develop/test-throttle-service-limits.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 09/17/2021
+ms.date: 11/09/2022
 ms.author: ryanwi
 ms.reviewer: arcrowe
 #Customer intent: As a developer, I want to understand the throttling and service limits I might hit so that I can test my app without interruption.
@@ -64,4 +64,4 @@ Throttling behavior can depend on the type and number of requests. For example,
 When you exceed a throttling limit, you receive the HTTP status code `429 Too many requests` and your request fails. The response includes a `Retry-After` header value, which specifies the number of seconds your application should wait (or sleep) before sending the next request. Retry the request.  If you send a request before the retry value has elapsed, your request isn't processed and a new retry value is returned. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended `Retry-After` delay and retry the request until it succeeds.
 
 ## Next steps
-Learn how to [setup a test environment](test-setup-environment.md).
+Learn how to [setup a test environment](test-setup-environment.md).

articles/aks/azure-disk-volume.md

@@ -24,6 +24,12 @@ This article assumes that you have an existing AKS cluster with 1.21 or later ve
 
 If you want to interact with Azure disks on an AKS cluster with 1.20 or previous version, see the [Kubernetes plugin for Azure disks][kubernetes-disks].
 
+The Azure Disks CSI driver has a limit of 32 volumes per node. The volume count will change based on the size of the node/node pool. Run the following command to determine the number of volumes that can be allocated per node:
+
+```console
+kubectl get CSINode <nodename> -o yaml
+```
+
 ## Storage class static provisioning
 
 The following table describes the Storage Class parameters for the Azure disk CSI driver static provisioning:

articles/aks/azure-disks-dynamic-pv.md

@@ -15,7 +15,7 @@ ms.date: 07/21/2022
 A persistent volume represents a piece of storage that has been provisioned for use with Kubernetes pods. A persistent volume can be used by one or many pods, and can be dynamically or statically provisioned. This article shows you how to dynamically create persistent volumes with Azure Disks for use by a single pod in an Azure Kubernetes Service (AKS) cluster.
 
 > [!NOTE]
-> An Azure Disks can only be mounted with *Access mode* type *ReadWriteOnce*, which makes it available to one node in AKS. If you need to share a persistent volume across multiple nodes, use [Azure Files][azure-files-pvc].
+> An Azure disk can only be mounted with *Access mode* type *ReadWriteOnce*, which makes it available to one node in AKS. If you need to share a persistent volume across multiple nodes, use [Azure Files][azure-files-pvc].
 
 For more information on Kubernetes volumes, see [Storage options for applications in AKS][concepts-storage].
 
@@ -25,6 +25,12 @@ This article assumes that you have an existing AKS cluster with 1.21 or later ve
 
 You also need the Azure CLI version 2.0.59 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
 
+The Azure Disks CSI driver has a limit of 32 volumes per node. The volume count will change based on the size of the node/node pool. Run the following command to determine the number of volumes that can be allocated per node:
+
+```console
+kubectl get CSINode <nodename> -o yaml
+```
+
 ## Built-in storage classes
 
 A storage class is used to define how a unit of storage is dynamically created with a persistent volume. For more information on Kubernetes storage classes, see [Kubernetes Storage Classes][kubernetes-storage-classes].

articles/aks/concepts-storage.md

@@ -33,6 +33,9 @@ Kubernetes typically treats individual pods as ephemeral, disposable resources.
 
 Traditional volumes are created as Kubernetes resources backed by Azure Storage. You can manually create data volumes to be assigned to pods directly, or have Kubernetes automatically create them. Data volumes can use: [Azure Disks][disks-types], [Azure Files][storage-files-planning], [Azure NetApp Files][azure-netapp-files-service-levels], or [Azure Blobs][storage-account-overview].
 
+> [!NOTE]
+> The Azure Disks CSI driver has a limit of 32 volumes per node. Other Azure Storage services don't have an equivalent limit.
+
 ### Azure Disks
 
 Use *Azure Disks* to create a Kubernetes *DataDisk* resource. Disks types include:
@@ -43,13 +46,13 @@ Use *Azure Disks* to create a Kubernetes *DataDisk* resource. Disks types includ
 * Standard HDDs
 
 > [!TIP]
->For most production and development workloads, use Premium SSD.
+> For most production and development workloads, use Premium SSD.
 
-Since Azure Disks are mounted as *ReadWriteOnce*, they're only available to a single node. For storage volumes that can be accessed by pods on multiple nodes simultaneously, use Azure Files.
+Because Azure Disks are mounted as *ReadWriteOnce*, they're only available to a single node. For storage volumes that can be accessed by pods on multiple nodes simultaneously, use Azure Files.
 
 ### Azure Files
 
-Use *Azure Files* to mount a Server Message Block (SMB) version 3.1.1 share or Network File System (NFS) version 4.1 share backed by an Azure storage accounts to pods. Files let you share data across multiple nodes and pods and can use:
+Use [Azure Files][azure-files-volume] to mount a Server Message Block (SMB) version 3.1.1 share or Network File System (NFS) version 4.1 share backed by an Azure storage account to pods. Azure Files let you share data across multiple nodes and pods and can use:
 
 * Azure Premium storage backed by high-performance SSDs
 * Azure Standard storage backed by regular HDDs