John Peluso
John Peluso

Microsoft RD and CTO, AvePoint Public Sector

BIO

Eric Overfield
Eric Overfield

President and Co-Founder, PixelMill

BIO

Unique requirements for each department

Let’s face it. Departments have a different number of users, deal with different sensitivity of the information, and are overseen by different industry regulations—shouldn’t they have different policies for their Microsoft Teams?

A “one size fits all” approach typically results in departments handling more sensitive information relegated to email. Or conversely, other departments where time to market is crucial are hampered by the strict policies of the most rigorous department and may even resort to shadow IT.

With native Office 365 functionality, if you disable external sharing for the Department of Transportation you are disabling it for the Department of Revenue. If you allow Marketing to self-provision a Teams Team you are allowing HR to do it too.

We’ll show you how to overcome this barrier while also showing you how to create Team templates that can be cloned by each department for common use cases.

Learn how to:

Tailor a Team’s components such as tabs, apps, bots, and more for common use cases experienced by organizational departments.

Clone Team templates and leverage these “best practice” workspaces. We’ll also show you how to layer on governance and prevent configuration drift.

Setting up granular rules and policies for the different departments while ensuring users stay compliant with established governance standards.

Monitoring all tasks requested and their latest status within SharePoint Online, Microsoft Teams, and Groups.

Providing a set of services to end-users with defined approval processes such as site collection provisioning, permissions management, etc.

Distribute responsibility for performing common tasks to non-admin staff for tasks.

Register today and tailor Microsoft Teams to your unique departmental needs!

Dux Speaking