Solved Multiple instances of 3CX / single Teams tenant

[dashbrook]

Just a suggestion. The PowerShell scripts that are generated from 3CX to be used within Teams generating the plans, etc. need unique identifiers within them. The current scripts just create "3CX Dial Plan", etc. There is no unique identifier. This causes problems when you try to integrate multiple instances of 3CX.

I had to modify the scripts to add unique information for our 3CX installation in the UK which is different from our installation in the US. The user plan had to be modified also to match up with the UK plans.

 

[NickD_3CX]

Hi!

Indeed if you plan on using the same Teams and MS account for multiple 3CX installations, you will have to change the Names that are in the scripts so that each script from each 3CX system has unique names, exactly as you said.

We don't plan on adding some identifier in the immediate future as this is not the common setup and for most would just make it harder to read, plus it is easy to tweak before running the script, but we shall keep this as feedback for the future.

I will go ahead and mark this as 'Solved'.