Microsoft publishes official, step-by-step deployment guides for nearly every Modern Work service, but they’re scattered across Microsoft Learn, the Microsoft 365 Setup Portal, and the admin center. This page organizes the ones worth starting from by practice area, and covers what actually changes if you’re deploying into GCC, GCC High, or DoD instead of commercial.
Every guide below is a Microsoft resource, not something written here. Most are freely viewable; a handful of the more advanced ones live only in the Microsoft 365 admin center and require signing in with an appropriate admin role. Where Microsoft offers both a public Setup Portal version and an admin-center version of the same guide, we’ve linked whichever is easiest to reach.
Environments and licensing
Before you start any of the guides below, confirm which Microsoft cloud environment you’re actually deploying into. The guidance is broadly the same across environments, but availability, timing, and a few features are not.
Commercial (worldwide) is the environment nearly every organization outside the U.S. public sector uses. It gets new features first, and this is what the guides below assume unless noted otherwise.
GCC (Government Community Cloud) is for U.S. federal, state, local, and tribal agencies, and contractors handling data subject to U.S. government requirements. It has U.S.-only data residency and aligns with FedRAMP Moderate. Feature releases typically lag commercial.
GCC High adds isolation for organizations handling Controlled Unclassified Information (CUI) or subject to DFARS and ITAR requirements, most commonly Defense Industrial Base contractors. Feature availability lags further behind GCC.
DoD is the most restricted environment, built exclusively for the U.S. Department of Defense and its mission partners, assessed against DoD Impact Level 5 controls.
One practical consequence for this page specifically: Microsoft’s advanced deployment guides, the interactive checklists linked throughout, are not available in GCC High, DoD, or Microsoft 365 operated by 21Vianet. If that’s your environment, use the Microsoft Learn documentation links instead and verify feature parity before you plan a rollout around any specific capability.
Deployment guides by practice area
Frequently Asked Questions
Are these Microsoft's own guides, or written by Modern Work Weekly?
Every link on this page goes to an official Microsoft resource: Microsoft Learn documentation or a Microsoft 365 Setup Portal guide. This page doesn’t rewrite Microsoft’s guidance, it organizes it by Modern Work practice area so you don’t have to hunt across learn.microsoft.com and the admin center to find the right starting point.
Do I need to sign in to use these guides?
The Microsoft Learn documentation links work for anyone. The Microsoft 365 Setup Portal guides (the ones with step-by-step checklists) are also publicly viewable without signing in, though a few advanced guides are admin-center-only and require signing in to a tenant with an appropriate admin role, most commonly Global Reader to view or Global Administrator to make changes.
What's the difference between GCC, GCC High, and DoD?
All three are Microsoft’s U.S. government cloud environments, ordered by isolation level. GCC is for federal, state, and local agencies and contractors needing U.S. data residency and FedRAMP Moderate alignment. GCC High adds isolation for organizations handling Controlled Unclassified Information (CUI) and DFARS or ITAR requirements. DoD is the most restricted, built exclusively for the Department of Defense. Feature availability lags behind commercial in that order too, so check a workload’s availability before you plan around it.
Can I use these advanced deployment guides in GCC High or DoD?
No. Microsoft’s advanced deployment guides in the admin center and Setup Portal are not available in GCC High, DoD, or Microsoft 365 operated by 21Vianet. If you’re in one of those environments, go directly to the Microsoft Learn documentation for the product instead, and confirm feature parity for your environment before you plan a rollout around it.
