--- title: "Outlook mobile add-ins in GCC and GCC High environments" slug: "using-the-outlook-mobile-add-in-within-gcc-environments" description: "Mobile add-ins are off by default in GCC and GCC High. What turning them on unlocks outside the FedRAMP boundary, and where to find the PowerShell steps." updated: 2026-06-29T21:04:52.000Z canonical: "https://help.opensense.com/docs/using-the-outlook-mobile-add-in-within-gcc-environments" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.opensense.com/llms.txt > Use this file to discover all available pages before exploring further. # Outlook mobile add-ins in GCC and GCC High environments ## Overview In Microsoft 365 GCC and GCC High environments, mobile add-ins are disabled by default. Even if you deploy them through the Microsoft 365 **Integrated Apps** portal, they don't load on mobile devices. To turn on Outlook mobile add-ins, your organization updates the Microsoft 365 tenant configuration with Exchange Online PowerShell. How it shows up on each device:
Android
The Add-ins option is missing from the app's settings.
iOS
Opening add-ins shows the message "This account does not support Add-ins."
## Tenant configuration considerations :::caution[Review this section before you run the cmdlet] Setting `OutlookMobileGCCRestrictionsEnabled` to `$false` is an all-or-nothing toggle. Besides turning on mobile add-ins, it unlocks several features that Microsoft places outside the FedRAMP boundary for GCC tenants. Your security or compliance team should decide whether this setting is right for your organization before you change it. ::: :::note[This is a Microsoft restriction] Opensense is compatible with GCC and GCC High environments. These considerations come from Microsoft's tenant-level restrictions, not from Opensense. ::: ### What this setting unlocks When `OutlookMobileGCCRestrictionsEnabled` is set to `$false`, these features turn on along with mobile add-ins: - Multi-account support (personal or non-GCC accounts on the same device) - Non-Microsoft third-party services - In-app support and diagnostic data submission (HelpShift) - Microsoft services outside the GCC boundary (for example, Bing and Cortana) - Third-party calendar apps (Facebook, Wunderlist, Evernote, Meetup) - Third-party storage providers - Office Lens (camera and scanning features) - Expanded file picker beyond email attachments ## Turning on mobile add-ins When your security or compliance team has reviewed the considerations above and approved the change, run the Exchange Online PowerShell cmdlet by following Microsoft's instructions: [Using Outlook for iOS and Android in the Government Community Cloud](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/outlook-for-ios-and-android-in-the-government-cloud). Microsoft's article covers the exact command, how to revert the change, and how long it takes to take effect. :::note[Support for the cmdlet] Opensense does not provide direct support for Exchange Online PowerShell configuration. For questions about running the cmdlet or its effect on your tenant, contact Microsoft support or your IT administrator. ::: ## What's next - [Opensense Outlook Add-in integration with GCC High environments](https://help.opensense.com/docs/opensense-add-in-integration-with-gcc-high-environments): GCC High requirements and deployment. - [Using the Opensense Outlook Add-in on iOS](https://help.opensense.com/docs/how-to-access-opensense-outlook-add-in-on-ios) - [Using the Opensense Outlook Add-in on Android](https://help.opensense.com/docs/how-to-access-opensense-outlook-add-in-on-android)