KB26755: MicroStrategy Mobile 10 and EMM(MDM) Supported Configurations

Initially, Enterprise Management Mobility (EMM) vendors offered two methods for incorporating their libraries into mobile apps: app wrapping or native SDK integration. Strategy customers have used both options. Strategy initially chose to develop native support on iOS for AirWatch, MobileIron and Good Dynamics as these three vendors are the leaders in the market and we received the most demand for these products from customers. Strategy customers using these EMM solutions can integrate Strategy natively by leveraging one of the three EMM specific Mobile SDKs Strategy has released. 
As of the release of Strategy 10.6, Strategy is moving towards an AppConfig based strategy for Mobile EMM based deployments. Refer to KB319511  for more information.
App Wrapping
App wrapping is often a very viable solution and it works for many customers, but unfortunately Strategy doesn’t have a way to code, debug or fix any issues that might occur when using a wrapper, as the EMM vendor owns the wrapper code. As such, we can’t provide resolution support to customers using this deployment method. This dilemma affects all other mobile app vendors, not just Strategy.
AppConfig
The good news is Apple has recently opened up EMM APIs on the device which has enabled Strategy to work on a solution that will help customers. Our approach to supporting EMMs has shifted from vendor specific SDK level integrations to a standards based approach leveraging AppConfig (ACE) guidelines (https://www.appconfig.org/). The AppConfig guidelines utilize native EMM APIs for iOS and Android mobile platforms and don’t rely on an EMM vendor specific SDK. The AppConfig-compliant Strategy Mobile application for iOS is available as of Strategy 10.5, distributed as the standard iOS SDK download. Strategy has implemented these guidelines in the Android SDK for Strategy Mobile 10.7.
Note on Feature Support: To determine what features Strategy Mobile secured by Good Dynamics, AirWatch or MobileIron supports, check the MSDZ Mobile SDK Documentation. If the feature desired is not listed, check with the 3rd party EMM provider to determine whether the desired feature is supported in their respective SDK. If the 3rd party EMM provider does support the desired feature, proceed to log an idea on our Idea Exchange (sample subject line: "Support feature X with Strategy Mobile version Y secured by EMM Z"). If the 3rd party EMM provider does not support the desired feature, proceed to log the enhancement with that respective EMM provider.
 
EMM integration support:

Note: Where a Strategy Mobile version is specified, the capability was introduced to and is available from that version or newer.
iOS and Xcode version certification:

 
EMM feature support for iOS:

 
Additional notes on feature support:

• "Yes" and "No" refer to the scenario whether our integration supports the feature. "N/A" denotes the case where the MDM SDK does not support the feature.
• ACE denotes the case where the MDM vendor is ACE or AppConfig-Compliant, allowing ourAppConfig-compliant app to be used without the MDM-specific SDK, without app-wrapping.
• Tunneling. Note that there is no guarantee that the MDM SDK is able to intercept every kind of network communication our application makes. Each MDM may have disclaimers limiting the API calls this feature covers.
• Logging. There are no plans at the moment to support MDM logging.