Merge pull request #227573 from MicrosoftDocs/main

Merge main to live, 4 AM

Author: v-ccolin

articles/active-directory-b2c/azure-ad-b2c-global-identity-proof-of-concept-funnel.md

@@ -28,7 +28,7 @@ The following block diagram shows the proof of concept. The guidance will show h
 
 1. [Create a tenant.](../active-directory-b2c/tutorial-create-tenant.md)
 
-1. [Configure federations to each Azure AD B2C tenant/policy combination](tenant-management.md)
+1. [Configure federations to each Azure AD B2C tenant/policy combination](../active-directory-b2c/tutorial-create-user-flows.md?pivots=b2c-user-flow)
 
 1. Configure client_id mapping to region – use [lookup claim transformation](general-transformations.md) to emulate.
 

articles/active-directory/authentication/how-to-mfa-number-match.md

@@ -305,7 +305,7 @@ GET https://graph.microsoft.com/beta/authenticationMethodsPolicy/authenticationM
 
 ### When will my tenant see number matching if I don't use the Azure portal or Graph API to roll out the change?
 
-Number match will be enabled for all users of Microsoft Authenticator push notifications after May 8, 2023. We had previously announced that we will remove the admin controls and enforce the number match experience tenant-wide for all users of Microsoft Authenticator push notifications starting May 8, 2023. After listening to customers, we will extend the availability of the rollout controls for a few more weeks. 
+Number match will be enabled for all users of Microsoft Authenticator push notifications after May 8, 2023. We had previously announced that we will remove the admin controls and enforce the number match experience tenant-wide for all users of Microsoft Authenticator push notifications starting February 27, 2023. After listening to customers, we will extend the availability of the rollout controls for a few more weeks. 
 
 Relevant services will begin deploying these changes after May 8, 2023 and users will start to see number match in approval requests. As services deploy, some may see number match while others don't. To ensure consistent behavior for all your users, we highly recommend you use the Azure portal or Graph API to roll out number match for all Microsoft Authenticator users. 
 

articles/active-directory/reports-monitoring/reference-azure-ad-sla-performance.md

@@ -44,20 +44,20 @@ To help you plan for moving workloads to Azure AD, we publish past SLA performan
 
 The SLA attainment is truncated at three places after the decimal. Numbers are not rounded up, so actual SLA attainment is higher than indicated. 
 
-| Month     | 2021    | 2022    |
-| ---       | ---     | ---     |
-| January   |         | 99.998% |
-| February  | 99.999% | 99.999% |
-| March     | 99.568% | 99.998% |
-| April     | 99.999% | 99.999% |
-| May       | 99.999% | 99.999% |
-| June      | 99.999% | 99.999% |
-| July      | 99.999% | 99.999% |
-| August    | 99.999% | 99.999% |
-| September | 99.999% | 99.998% |
-| October   | 99.999% | 99.999% |
-| November  | 99.998% | 99.999% |
-| December  | 99.978% | 99.999% |
+| Month     | 2021    | 2022    | 2023    |
+| ---       | ---     | ---     | ---     |
+| January   |         | 99.998% | 99.998% |
+| February  | 99.999% | 99.999% | |
+| March     | 99.568% | 99.998% | |
+| April     | 99.999% | 99.999% | |
+| May       | 99.999% | 99.999% | |
+| June      | 99.999% | 99.999% | |
+| July      | 99.999% | 99.999% | |
+| August    | 99.999% | 99.999% | |
+| September | 99.999% | 99.998% | |
+| October   | 99.999% | 99.999% | |
+| November  | 99.998% | 99.999% | |
+| December  | 99.978% | 99.999% | |
 
 ### How is Azure AD SLA measured? 
 

articles/aks/azure-disk-csi.md

@@ -30,7 +30,7 @@ In addition to in-tree driver features, Azure Disks CSI driver supports the foll
   - `Premium_ZRS`, `StandardSSD_ZRS` disk types are supported. ZRS disk could be scheduled on the zone or non-zone node, without the restriction that disk volume should be co-located in the same zone as a given node. For more information, including which regions are supported, see [Zone-redundant storage for managed disks](../virtual-machines/disks-redundancy.md).
 - [Snapshot](#volume-snapshots)
 - [Volume clone](#clone-volumes)
-- [Resize disk PV without downtime(Preview)](#resize-a-persistent-volume-without-downtime-preview)
+- [Resize disk PV without downtime](#resize-a-persistent-volume-without-downtime)
 
 > [!NOTE]
 > Depending on the VM SKU that's being used, the Azure Disks CSI driver might have a per-node volume limit. For some powerful VMs (for example, 16 cores), the limit is 64 volumes per node. To identify the limit per VM SKU, review the **Max data disks** column for each VM SKU offered. For a list of VM SKUs offered and their corresponding detailed capacity limits, see [General purpose virtual machine sizes][general-purpose-machine-sizes].
@@ -281,17 +281,7 @@ outfile
 test.txt
 ```
 
-## Resize a persistent volume without downtime (Preview)
-
-> [!IMPORTANT]
-> Azure Disks CSI driver supports expanding PVCs without downtime (Preview).
-> Follow this [link][expand-an-azure-managed-disk] to register the disk online resize feature.
-> 
-> az feature register --namespace Microsoft.Compute --name LiveResize
-> 
-> az feature show --namespace Microsoft.Compute --name LiveResize
->
-> Follow this [link][expand-pvc-with-downtime] to expand PVCs **with** downtime if you cannot try preview feature.
+## Resize a persistent volume without downtime
 
 You can request a larger volume for a PVC. Edit the PVC object, and specify a larger size. This change triggers the expansion of the underlying volume that backs the PV.
 
@@ -460,4 +450,4 @@ The output of the command resembles the following example:
 [az-on-demand-bursting]: ../virtual-machines/disk-bursting.md#on-demand-bursting
 [enable-on-demand-bursting]: ../virtual-machines/disks-enable-bursting.md?tabs=azure-cli
 [az-premium-ssd]: ../virtual-machines/disks-types.md#premium-ssds
-[general-purpose-machine-sizes]: ../virtual-machines/sizes-general.md
+[general-purpose-machine-sizes]: ../virtual-machines/sizes-general.md

articles/app-service/quickstart-arc.md

@@ -52,7 +52,7 @@ Get a sample Node.js app using Git and deploy it using [ZIP deploy](deploy-zip.m
 git clone https://github.com/Azure-Samples/nodejs-docs-hello-world
 cd nodejs-docs-hello-world
 zip -r package.zip .
-az webapp config appsettings set --resource-group myResourceGroup --name --settings SCM_DO_BUILD_DURING_DEPLOYMENT=true
+az webapp config appsettings set --resource-group myResourceGroup --name <app-name> --settings SCM_DO_BUILD_DURING_DEPLOYMENT=true
 az webapp deployment source config-zip --resource-group myResourceGroup --name <app-name> --src package.zip
 ```
 

articles/azure-arc/data/validation-program.md

@@ -34,6 +34,7 @@ To see how all Azure Arc-enabled components are validated, see [Validation progr
 
 |Solution and version | Kubernetes version | Azure Arc-enabled data services version | SQL engine version | PostgreSQL server version
 |-----|-----|-----|-----|-----|
+| Unity XT |1.25.4|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
 | PowerStore T|1.25.4|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
 | Dell EMC PowerFlex |1.21.5|1.4.1_2022-03-08|15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |
 | PowerFlex version 3.6 |1.21.5|1.4.1_2022-03-08|15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |
@@ -45,6 +46,7 @@ To see how all Azure Arc-enabled components are validated, see [Validation progr
 
 |Solution and version | Kubernetes version | Azure Arc-enabled data services version | SQL engine version | PostgreSQL server version
 |-----|-----|-----|-----|-----|
+|HPE Superdome Flex 280 | 1.26.0 | 1.15.0_2023-01-10 | 16.0.816.19223 | Postgres 14.5(ubuntu 20.04)|
 |HPE Apollo 4200 Gen10 Plus | 1.22.6 | 1.11.0_2022-09-13 |16.0.312.4243|12.3 (Ubuntu 12.3-1)|
 |HPE Superdome Flex 280|1.20.0|1.8.0_2022-06-14|16.0.41.7339|12.3 (Ubuntu 12.3-1)
 

articles/azure-video-indexer/deploy-with-bicep.md

@@ -23,7 +23,7 @@ In this tutorial, you create an Azure Video Indexer account by using [Bicep](../
 
 The Bicep file used in this tutorial is:
 
-:::code language="bicep" source="~/media-services-video-indexer/ARM-Quick-Start/avam.template.bicep":::
+:::code language="bicep" source="~/media-services-video-indexer/Deploy-Samples/ArmTemplates/avam.template.bicep":::
 
 One Azure resource is defined in the bicep file: