Shared screen in custom Mesh environment

CameronMicka  Thanks Cameron but, that's not going to cut it.  I get the idea of how it might be convenient to allow a degree of post build environment customization via the event customization tool for non technical users. However, it is absolutely essential that EVERYTHING that is is possible to do in the customization tool be available to be done via code in Unity / cloud scripting for the pro developer so it can be baked into the environment and the relevant Url's etc supplied via code. 

For context the scenario I am talking about involves accessing medical data including videos 3D models of patient anatomy built from CT scans etc selected at runtime from dataverse / blob storage hosted data accessed via cloud scripting and pulling them into the Unity scene at runtime to facilitate case reviews.  If it is not going to be possible to do that sort of thing and the event customization route is the only way to bring Gameobjects into the environment at runtime (your "artifacts")  then Mesh will very quickly be relegated to being an office toy rather than a serious business tool.

I can already load objects at runtime using a tool like https://assetstore.unity.com/packages/tools/modeling/trilib-2-model-loading-package-157548 and point it to blob storage.  However, the promise of Mesh was that it was all secure, closely coupled to Azure, the Microsoft graph etc and that you would be able to bring in back end data to the mesh environment at runtime.    Do I need to look outside mesh at packages like TriLib2 to code bringing in my Azure hosted data and to manipulate load / manipulate "artifacts" or is Mesh actually going to deliver the ability for pro developers to build proper business tools with all the security etc. 

If there is way, and I'd be truly shocked if there isn't, to make the various runtime elements "artifacts" available to those building the environments I would very strongly suggest that Microsoft get it out in front of Unity developers and permit them to realize its potential ASAP because right now Mesh appears to be positioned at the toy end of the spectrum.

The surgeons I work with aren't too interested in holding their pre operative planning meetings on the flight deck of a a spaceship while toasting marshmallows - they are interested in serious collaboration tools which have the potential to improve patient outcomes by ensuring that all involved can see the relevant data and collaborate over that data in a 3D context.  I appreciate that it is at the preview stage but it has been a VERY long wait for mesh to hit public preview and what has been released so far in terms of documentation, tutorials etc. is frankly pitiful - it makes it look like Microsoft isn't really interested in Mesh anymore, which I very much hope isn't the case.