I want to deploy multiple Teams Recording Bot with more than one Bot Channels Registration in AKS

I want to deploy multiple Teams Recording Bot with more than one Bot Channels Registration in AKS.

As an example, tenant A and tenant B have their own bot Channels Registration,
Use different Teams Recording Bot for each.
I want to achieve that with one VM.

To achieve this, I considered how to deploy multiple TeamsRecordingBots in one VM with separate namespaces.

Describe the issue
First, I deployed the first bot by following the steps below.
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/master/Samples/V1.0Samples/AksSamples/teams-recording-bot/docs/deploy/aks.md

Next, create a new namespace and secret with "Deploy bot to AKS".
When I tried to deploy the second bot, I got the following error:

Error: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "teams-recording-bot-tcp-services" in namespace "ingress-nginx" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "teams-recording-bot2": current value is "teams-recording-bot"

On the other hand, I thought that deploying another nginx-ingress might solve the problem.
I made the following changes in "ingress-nginx.bat" and executed the bat file.

・ 4th line kubectl create namespace ingress-nginx2
・ Line 14 --namespace ingress-nginx2
・ Line 20 --set controller.extraArgs.tcp-services-configmap = ingress-nginx / teams-recording-bot2-tcp-services

However, the following error occurs when executing the bat file.

"Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole" nginx-ingress-ingress-nginx "in namespace" "exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "ingress-nginx2": current value is "ingress-nginx" "

Expected behavior
Create multiple namespaces in one VM and deploy TeamsRecordingBot

Start with docs/deploy/aks.md and the ingress-nginx.bat deployment steps mentioned in the issue. Reproduce the second deployment using separate namespaces and review the Helm ownership errors for the shared ConfigMap and ClusterRole. Done means the documented deployment supports multiple Teams Recording Bots with separate bot registrations on one VM.