AKS-hosted AWX operator's dynamic PVC must be switched to a CSI-based PVC

I have the AWX operator installed in an AKS environment. When creating the PVC, we initially used a dynamic provisioning approach with the storage class provisioner type kubernetes.io/azure-disk, but this is now deprecated. We need to switch to the disk.csi.azure.com provisioner type.

We followed the migration steps for transitioning from in-tree to CSI dynamic volumes as outlined in the Microsoft guide:

After running the script, a new PVC has been created. Where should we make changes to attach the newly created PVC to AWX, so we can test whether the application is functioning as expected with the new PVC and PV?

#-> kubectl get sc
NAME                                                 PROVISIONER                RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
azurefile                                            file.csi.azure.com         Delete          Immediate              true                   279d
azurefile-csi                                        file.csi.azure.com         Delete          Immediate              true                   279d
azurefile-csi-premium                                file.csi.azure.com         Delete          Immediate              true                   279d
azurefile-premium                                    file.csi.azure.com         Delete          Immediate              true                   279d
default (default)                                    disk.csi.azure.com         Delete          WaitForFirstConsumer   true                   279d
manage-azr-hvu-iautomatecluster-development-retain   kubernetes.io/azure-disk   Retain          WaitForFirstConsumer   true                   245d
manage-premium-retain                                disk.csi.azure.com         Retain          WaitForFirstConsumer   true                   251d
managed                                              disk.csi.azure.com         Delete          WaitForFirstConsumer   true                   279d
managed-csi                                          disk.csi.azure.com         Delete          WaitForFirstConsumer   true                   279d
managed-csi-premium                                  disk.csi.azure.com         Delete          WaitForFirstConsumer   true                   279d
managed-premium                                      disk.csi.azure.com         Delete          WaitForFirstConsumer   true                   279d

#-> kubectl get pv,pvc -n awx
NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                   STORAGECLASS                                         REASON   AGE
persistentvolume/pvc-043348db-676a-42bb-a0a5-3440309f9600   100Gi      RWO            Retain           Bound    awx/postgres-13-awx-dev-postgres-13-0   manage-azr-hvu-iautomatecluster-development-retain            245d

NAME                                                                             STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                                         AGE
persistentvolumeclaim/**csi-postgres-13-awx-dev-postgres-13-0**                      Pending                                                                        default                                              25d
persistentvolumeclaim/manage-azr-hvu-iautomatecluster-development-retain-claim   Pending                                                                        manage-azr-hvu-iautomatecluster-development-retain   245d
persistentvolumeclaim/postgres-13-awx-dev-postgres-13-0                          Bound     pvc-043348db-676a-42bb-a0a5-3440309f9600   100Gi      RWO            manage-azr-hvu-iautomatecluster-development-retain   245d

csi-postgres-13-awx-dev-postgres-13-0 is the new pvc and postgres-13-awx-dev-postgres-13-0 is the old pvc.

Need Assistance with steps to be perform for this migration or change of mapping.