Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Microsoft Teams plays a key role to facilitate secure and efficient communication across various government sectors and agencies. Government entities handle sensitive and confidential data, and there's a crucial need for cloud platforms that are secure and compliant. To meet the stringent security requirements, the specialized government cloud services offered are:
Government Community Cloud (GCC), GCC High, Department of Defense (DoD) are limited for use within the United States.
Teams app capabilities
Teams is compatible with all Microsoft 365 Government environments, but the capabilities and features vary by tenant. Due to security and compliance restrictions, all the features available in commercial tenants might not be accessible in government tenants while other features take time to roll out in government tenant. We recommend that you have the understanding of the Teams apps and its capabilities supported in government tenants to ensure effective utilization.
The following table details the Teams apps and its capabilities for GCC, GCC High, and DoD:
| GCC | GCC High | DoD | |
|---|---|---|---|
| Apps | |||
| Apps built by Microsoft | ✔️ | ✔️ | ✔️ |
| Third-party apps | ✔️ | ❌ | ❌ |
| Custom apps built for your org (LOB apps) distributed and used in specific organization | ✔️ | ✔️ | ✔️ |
| Upload a custom app | ✔️ | ❌ | ❌ |
| App capabilities | |||
| Tabs | ✔️ | ✔️ | ✔️ |
| Bots | ✔️ | ✔️ | ✔️ |
| Message extensions | ✔️ | ✔️ | ✔️ |
| Message actions | ✔️ | ✔️ | ✔️ |
| Cards: Adaptive, Hero, Thumbnail, Microsoft 365 connector, Receipt, Sign in, and OAuth cards | ✔️ | ✔️ | ✔️ |
| Dialogs (referred as task modules in TeamsJS v1.x) | ✔️ | ✔️ | ✔️ |
| Link unfurling | ✔️ | ✔️ | ✔️ |
| Meeting extensions | ✔️ | ✔️ | ✔️ |
| Webhooks and connectors | ✔️ | ✔️ | ❌ |
| Workflows | ✔️ | ❌ | ❌ |
| Experiences | |||
| Teams Store | ✔️ | ✔️ | ✔️ |
| In-context Teams Store or app flyouts | ✔️ | ✔️ | ✔️ |
| Manage apps in Teams | ✔️ | ✔️ | ✔️ |
| Manage apps in Teams Admin Center | ✔️ | ✔️ | ✔️ |
| Graph APIs | ✔️ | ✔️ | ✔️ |
| Developer Portal for Teams | ✔️ | ❌ | ❌ |
For more information on Graph API, see Graph API for Government clouds.
Note
- Third-party apps are turned off by default for GCC and aren't available for GCC High and DoD. To turn on third-party apps for GCC, see manage org-wide app settings for Microsoft 365 Government.
- GCC High supports Incoming Webhooks only.
Plan to deploy Teams in government clouds
To deploy Teams in GCC, GCC High, or DoD, you must purchase a suitable Microsoft 365 Government plan. US federal, state, local or tribal government entity, or other entities that handle data subject to government regulations can opt for a government cloud service license. For more information, see Teams for Government.
Compliance with third-party services
Here are few pointers to consider while connecting with third-party services from government clouds:
- Understand that by enabling third-party communication, the communication is processed through the third party and not Microsoft.
- Understand that enabling bots extend your system boundary beyond this tenant, and is based on the bot you choose to use. You must ensure that the bot meets the compliance requirements including FedRAMP, DFARS, and ITAR.
- Understand that Microsoft doesn't endorse and makes no warranties concerning the security of third parties that the customer allows to connect with their service.
- Mitigate risks associated with connecting to third-party bots in their services.
- Evaluate the risk and compliance of any endpoint and URL that the users connect to.
See also
Platform Docs