Can I set Multi Account Containers default containers with endpoint deployment?
I am installing Firefox via microsoft endpoint, and deploying multi account containers with the OMA-URI policy for extensions. (this blog page is super helpful! https://securitygeneralist.blogspot.com/2019/08/auto-installing-extensions-on-firefox.html )
The extension by default has containers for Personal, Work, Banking, Shopping.
Is there a way to automatically remove that default container list as part of the install?
Even better, is there a way to create a different default containers list through Endpoint?
Modified by Chris
We currently don't support using enterprise policy to configure containers, but that's an interesting idea and might not be too hard to implement...Read this answer in context 👍 0
All Replies (5)
We currently don't support using enterprise policy to configure containers, but that's an interesting idea and might not be too hard to implement...
Thanks for the answer!
If it helps decide how to improve this, the specific social problem here is showing users a setup screen with a Personal container might lead to people going "oh they gave me a space for personal browsing on the work laptop!" which is... sorta the wrong impression for a corporate setup :) We'll tackle it with training for now. Thanks.
Do y'all use/recommend containers for specific things in your company?
I know it can be difficult to communicate the benefits of containers to a layperson, so I'm interested in knowing how you're doing it.
In short, multiple Outlook and Teams logins.
Many of our clients give our employees email addresses on their systems. So one employee might have 3 different clients they log in to, they will set up their own container for each. The separate space for Teams lets them sign in to multiple at once, and the container won't pick up the laptop login to the internal company Teams.
Some clients give us virtual desktops to create their own spaces, I see the containers as a lighter variation of that.
( * and I know I just said our employees will manage their client lists, but at the start I asked about a premade list, I was just thinking a premade container for "Internal" or "Non-Client" might be better than an empty set.)
So I've opened a bug for this:
It should be pretty straightforward, but I don't have timelines.
But we'll track any work there.