The DoD’s Cross-Command Telework Platform Expires Soon, What’s Next?
Enabling command-level controls in a centralized tenant

The DoD’s Cross-Command Telework Platform Expires Soon, What’s Next?

The following is an excerpt from an article Jay co-authored in AvePoint’s series on how the US Department of Defense can take advantage of Microsoft 365 in a post-pandemic world from the AvePoint Blog. Click here for the full article.

Microsoft has made Office 365 VERY simple to use and has robust security features, but it also has a central architecture.

Being under a central tenant is advantageous in that it allows quick collaboration and removes collaboration silos among/within the different commands. However, there are some configurations and settings that follow a “one-tenant, one rule” policy that can complicate each command’s ability to tailor the environment to their specific needs or protect different types of data in different ways.

For example: DCAA is going to have strict requirements over contractor access to audit data and workspace management, while agencies like CENTCOMDTRA, and MDA may lean heavily on contractors to manage their own collaborative workspaces and be key players in information collection.

With native controls, each of these agencies’ contractors will have the same privileges, access to workspace management and creation, and deployment of security features against workspace-required manual intervention. More specifically, if DCAA wants to exclude contractors from administering their SharePoint site collections, then no contractor across the entire DISA tenant can be a SharePoint Service Administrator, period.

For details on this and the rest of the series from AvePoint and our partners, supporting the DOD’s move to Microsoft 365’s Modern Workplace platform, click through or click on one of the below articles from the series:

Leave a Reply