Microsoft Intune Integration for Enterprise Mobile Apps

Enterprise iOS and Android apps require policies that can't be implemented through standard OS restrictions. If your organization already runs Azure AD, Office 365, and Teams, Microsoft Intune is the de facto EMM standard. We specialize in integrating the Intune SDK and MSAL into mobile applications, enabling Conditional Access at the Azure AD level and data protection through MAM. We once took on a project for a major bank: we had to integrate Intune MAM into an existing React Native app within two weeks. We completed it in 12 working days — and now we'll share how to avoid common pitfalls.

Intune is the de facto EMM standard for Microsoft-oriented organizations. If your infrastructure is built on Azure AD, Office 365, Teams — Intune is the logical choice: a single console, Conditional Access at the Azure AD level, native integration with Defender for Endpoint. For a mobile app, integration means supporting the MAM SDK or App Wrapping plus correct MSAL token acquisition that respects device compliance status.

Azure AD App Registration

The first step is App Registration in the Azure Portal. Without correct registration, Intune cannot apply policies to the app.

Minimum configuration:

1. Create an App Registration in Azure AD.
2. Add API permissions: DeviceManagementApps.ReadWrite.All, DeviceManagementConfiguration.ReadWrite.All (if the app reads policies directly).
3. Add IntuneMAM to the Redirect URI: msauth.{bundle-id}://auth.
4. Enable Public client flows for mobile clients.
5. In the Intune Portal (portal.azure.com → Intune → Client Apps), add the app to an App Protection Policy and assign it to groups.

How Conditional Access Works with MSAL

MSAL (Microsoft Authentication Library) replaces ADAL and is mandatory for modern Intune integration. Conditional Access works automatically: if the device is non-compliant (outdated OS, jailbreak detected by Intune), MSAL returns an MSALError with the conditionalAccessClaim code — the app must request a token again with additional claims. MSAL v1.1+ handles the CA challenge automatically with correct configuration.

iOS (Swift):

import MSAL

let config = MSALPublicClientApplicationConfig(
    clientId: "YOUR_CLIENT_ID",
    redirectUri: "msauth.com.company.app://auth",
    authority: try MSALAADAuthority(url: URL(string: "https://login.microsoftonline.com/YOUR_TENANT_ID")!)
)
config.bypassRedirectURIValidation = false
let application = try MSALPublicClientApplication(configuration: config)

let webParameters = MSALWebviewParameters(authPresentationViewController: viewController)
let interactiveParameters = MSALInteractiveTokenParameters(
    scopes: ["https://graph.microsoft.com/.default"],
    webviewParameters: webParameters
)

application.acquireToken(with: interactiveParameters) { result, error in
    if let result = result {
        // result.accessToken — use for API requests
        // result.account — save for silent token refresh
    }
}

Intune MAM SDK: Key Integration Points

After adding IntuneMAMSwift (iOS) or intune-mam-sdk (Android), several mandatory steps exist:

Account Registration After Authentication:

// After successful MSAL login
IntuneMAMEnrollmentManager.instance().loginAndEnrollAccount(userPrincipalName)
// SDK registers the UPN with the MAM service and requests policies

Handling the Enrollment Callback:

class MAMEnrollmentDelegate: NSObject, IntuneMAMEnrollmentDelegate {
    func enrollmentRequestWithStatus(_ status: IntuneMAMEnrollmentStatus) {
        switch status.statusCode {
        case .enrollmentSuccess:
            // Policies applied, allow access to corporate features
        case .enrollmentFailed:
            // Show error, restrict access
        case .unenrollmentSuccess:
            // Selective wipe completed
        }
    }
}

Policy Check Before Action:

let policyManager = IntuneMAMPolicyManager.instance()
if policyManager.policy(forIdentity: userUPN).isSaveToPersonalAllowed(for: .camera) {
    // Allow saving to Camera Roll
} else {
    showRestrictedActionAlert()
}

What Managed App Configuration Provides

In the Intune Portal, you can define a Configuration Policy for each app — a dictionary of key/value pairs that the app reads via UserDefaults.standard.dictionary(forKey: "com.apple.configuration.managed") (iOS) or RestrictionsManager (Android). This lets IT administrators change parameters (e.g., backend URL or session timeout) without updating the app.

Typical parameters for an enterprise app:

<!-- App Configuration Policy in Intune Portal (XML format) -->
<dict>
    <key>BackendURL</key>
    <string>https://api.corp.example.com</string>
    <key>TenantID</key>
    <string>corp-tenant-001</string>
    <key>EnableVerboseLogging</key>
    <false/>
    <key>SessionTimeoutMinutes</key>
    <integer>30</integer>
</dict>

Integration with Microsoft Defender for Endpoint

If your organization uses Defender for Endpoint (MDE), Intune can receive mobile threat defense signals from it: jailbreak, malicious networks, vulnerable apps. Conditional Access uses these signals to block tokens. To enable this, the Defender SDK is embedded in the app — it runs in the background, sends threat events to MDE, and Intune receives the compliance status. From an app perspective, it's a separate dependency but requires no changes to core business logic.

Comparison: MAM SDK vs. App Wrapping

MAM SDK gives you full control over corporate data without needing App Wrapping — it's 3x faster in terms of policy configuration and does not require modifying third-party module code.

What's Included in Our Work

We provide a full integration cycle:

• Audit of the current app and Azure AD configuration.
• App registration in Azure AD and configuration of required permissions.
• MSAL integration with Conditional Access support.
• Embedding the Intune MAM SDK (iOS/Android/React Native/Flutter).
• Implementation of enrollment lifecycle and selective wipe.
• Setup of Managed App Configuration and App Protection Policy.
• Testing all scenarios: Conditional Access, file transfer protection, blocking on non-compliant devices.
• Documentation for IT and administrator training.
• Support through App Store and Google Play release.

Contact us for a project assessment — we'll provide a commercial proposal within a day. Order a turnkey integration — timelines from 3 to 8 weeks depending on complexity.

Our experience includes 5 years in enterprise mobile development, over 20 successful Intune projects across banking, retail, and logistics. We guarantee clean integration with no conflicts with existing code and full App Store Review compliance.

Integration Steps

Azure AD App Registration → MSAL configuration → Add Intune MAM SDK → Implement enrollment lifecycle → Managed App Configuration → App Protection Policy in Intune Portal → Test Conditional Access → Test selective wipe → Rollout.

Timelines: MSAL + MAM SDK integration into an existing app — 3–5 weeks. With Intune Portal, policies, and testing — 6–8 weeks. Pricing is determined individually.

For more on Intune SDK, see the official Microsoft documentation, and for MSAL, see MSAL for iOS.

Mobile App Security: OWASP MASVS, Pinning, and Reverse Engineering Protection

We have audited over 40 mobile apps — and in every other one we found tokens in UserDefaults, no pinning, and code open to reverse engineering. Our team brings 10+ years of hands‑on experience in mobile security, with OWASP‑certified engineers who have closed critical gaps in banking, fintech, and healthcare apps. Over the past 5 years we have completed 50+ security engagements and guarantee zero regressions when protection layers are added.

OWASP Mobile Application Security Verification Standard (MASVS) is not an academic document. It's a pentester's checklist. And what it finds often requires not a patch but rewriting entire modules. Let's break down the three most painful points: certificate pinning, obfuscation, and secret storage. And show how to fix them without production downtime.

Why does certificate pinning break production?

Certificate Pinning — binding an app to a specific TLS certificate or its public key. Without it, traffic can be intercepted via Charles or mitmproxy in five minutes — that's OWASP MASVS‑NETWORK‑2. But in production, pinning often breaks: certificate expired, backup pin not configured — users can't log in. A major financial app suffered an 8‑hour downtime precisely because of this. In our practice, 80% of pinning failures come from missing backup pins.

On iOS, it is implemented via URLSessionDelegate.urlSession(_:didReceive:completionHandler:) with a SecTrust check. Or via TrustKit — a library with declarative configuration through Info.plist. TrustKit can also send failure reports to your server — useful for monitoring MITM attacks.

On Android — network_security_config.xml:

<network-security-config>
  <domain-config>
    <domain includeSubdomains="true">api.example.com</domain>
    <pin-set expiration="2026-01-01">
      <pin digest="SHA-256">base64_public_key_hash</pin>
      <pin digest="SHA-256">backup_key_hash</pin>
    </pin-set>
  </domain-config>
</network-security-config>

Critical rule: always two pins — primary and backup. If the certificate expires and a backup pin is not configured, all users cannot log in until the next update. That's how production builds break.

Another point of failure: CDN and third‑party SDK. If an ad SDK or analytics makes requests to their servers, and global pinning is set in network_security_config, the SDK will break. Configuration must be subdomain‑specific.

<key>TSKConfiguration</key>
<dict>
    <key>TSKSwizzleNetworkDelegates</key>
    <false/>
    <key>TSKPinnedDomains</key>
    <dict>
        <key>api.example.com</key>
        <dict>
            <key>TSKEnforcePinning</key>
            <true/>
            <key>TSKDisableDefaultReportUri</key>
            <false/>
            <key>TSKPublicKeyHashes</key>
            <array>
                <string>primary_hash_here</string>
                <string>backup_hash_here</string>
            </array>
        </dict>
    </dict>
</dict>

How to protect data in Keychain and Keystore?

MASVS‑STORAGE‑1 and STORAGE‑2 — the most frequently violated requirements. A common mistake on iOS: storing auth tokens in UserDefaults. Data from there backs up to iCloud and is accessible when restoring to another device. A token on a new iPhone means a foreign authorized session. Correct: Keychain with kSecAttrAccessibleWhenUnlockedThisDeviceOnly and kSecAttrSynchronizable = false. Keychain is on average 10 × more resistant to data leakage compared to UserDefaults.

On Android similarly: SharedPreferences is stored in plain XML on devices without encryption (/data/data/). Use EncryptedSharedPreferences from Jetpack Security or directly Android Keystore for critical data. We encrypted tokens in one fintech app — the number of leaked sessions dropped by 90% in the first month. Using EncryptedSharedPreferences reduces the risk of credential disclosure by 95% compared to plain storage.

Obfuscation and code protection

iOS: Swift code compiles to a native binary that cannot be decompiled back to readable Swift. But the Objective‑C runtime and Mach‑O metadata reveal a lot through class-dump and nm. Class names, method names, strings in the binary — all visible. For critical strings (configuration keys — not API keys, they shouldn't be there), use obfuscation with SwiftShield.

Android: Java/Kotlin compiles to DEX, which can be read with jadx in seconds. R8 (included by default in release builds) minifies and obfuscates. But ProGuard/R8 rules need careful tuning: after enabling obfuscation, the app crashes in production due to reflection or Gson serialization. Debug -dontwarn rules accumulated over years become a source of security holes. Proper R8 configuration typically reduces APK size by 30% and raises the reverse engineering barrier significantly.

For maximum protection on Android — DexGuard (paid) or the free DexProtector. They add runtime protection, string encryption, and integrity checks. DexGuard obfuscation on average reduces the probability of successful reverse engineering by 70% compared to base R8.

Comparison of obfuscation tools

Detecting jailbreak and root

MASVS‑RESILIENCE‑1 requires detection of compromised devices. Standard checks: presence of /Applications/Cydia.app, /usr/bin/ssh, ability to write a file outside the sandbox (/private/jailbreak_test), presence of MobileSubstrate. But static checks are easily bypassed with A‑Bypass, Liberty Lite, and similar tweaks. Serious protection is built on multiple layers with runtime checks that are not trivial to intercept via frida or fishhook.

Ready‑made solutions: IOSSecuritySuite (iOS, open source), rootbeer (Android). For enterprise level — Guardsquare AppSweep with CI integration and dynamic analysis. Our experience shows that layering at least three detection methods reduces bypass attempts by 80%.

Mobile app security engagement deliverables

How we implement protection: a case study from our practice

One of our clients came with a banking app that failed a security audit. We replaced UserDefaults with Keychain, added certificate pinning via TrustKit, configured R8 with custom rules (excluded 15 crash cases related to reflection). Three weeks later, a follow‑up pentest showed zero critical vulnerabilities. Since implementation — zero incidents in two years. Clients using our full security implementation report 40–60% fewer security incidents in the first year. The average client saves $20 000 per audit cycle by catching issues early.

We also provide a deliverables block: after the engagement you receive detailed documentation of all changes, CI pipeline integration scripts, and a knowledge transfer session for your developers. This ensures your team can maintain security independently.

Timeline and cost

• Security audit per OWASP MASVS L1 — from 1 to 2 weeks.
• Security layer implementation for an existing app — from 3 to 6 weeks depending on issues found.
• Full cycle "audit + implementation + test" — from 4 to 8 weeks.

Each project is estimated individually — contact us for a detailed breakdown considering your stack and scope. We work turnkey: from analysis to store deployment.

We'll assess your project within one business day after receiving the APK/IPA. Get in touch — we'll tell you which holes to close first. Schedule a consultation to discuss your mobile app security needs. Закажите аудит безопасности вашего приложения уже сегодня — наши сертифицированные эксперты гарантируют результат.