Hi! Thanks to answer.
I make a big workaround to make it work.
I created an C++ app (like a loader) and is the only EXE in the package. Other “exe” are renamed to “ex” with the idea the automated procedure don’t find and choice my laucher like the app to automaticly launch.
My c++ app launcher rename the “ex” to “exe”, then, run 3 signalling servers for 5.1 (placed in other folder). And last, run 3 instances of my ue app.
In the VMSS scale set I close the port 80-82 to avoid the 4.27 signalling servers reach the matchmaker, and open 90-92 to allow my 5.1 signalling servers reach the MM.
Eveything is working as spected, and automaticly.
When the VMSS machine starts, run my launcher, and the launcher start everything.
My problem NOW is the auto scalling. For some reason, when the 3 instances is in use, isn`t create a new VM instance.
The matchmaker is the original from the azure maketplace app. The VM with matchmaker is not tweaked at all.
In my CONFIG.JSON of every UE 5.1 Signalling Server, I edited and add some of the extra parameters from the CONFIG.JSON of 4.27 version automated created for the azure app.
What can I do to make the autoscale works??
Other problem is my Unreal App connect to my multiplayer server, and all is replicated fine, but Internet not work to see pages with Webbrowser plugin or to load the avatars from Ready Player Me…
Hope you can helpme.
Thanks!