Microsoft Intune with Flexopus: App distribution made easy
With the Microsoft Intune integration, IT administrators can centrally deploy the Flexopus app to all managed employee devices—without manual user configuration. Setup is performed once in the Intune Admin Center and then applies automatically to all relevant devices.
What is the Microsoft Intune integration?
Microsoft Intune is a cloud-based solution for Mobile Device Management (MDM) and Mobile Application Management (MAM). Through Intune, companies can centrally manage and distribute apps and configurations to employee devices.
The Flexopus integration leverages this capability: administrators store the domain configuration required for Flexopus directly in an Intune app configuration policy. When an employee opens the Flexopus app on their managed device, the domain value is transferred automatically—eliminating the need for manual entry.
What is the purpose of the integration?
Without Intune, users must manually enter a domain the first time they launch the Flexopus app—a value most employees do not know and which must first be communicated by the administrator. This leads to inquiries, errors, and additional effort.
With the Intune integration, this step is completely eliminated. Typical use cases:
- Large-scale rollouts: The app is deployed to hundreds or thousands of devices simultaneously without requiring individual user action.
- Automatic onboarding: New employees can use Flexopus immediately once their device is registered in the corporate network.
- Reduced support effort: IT teams receive no inquiries about domain entry because the value is automatically pre-filled.
- Uniform configuration: All devices receive the same, correct configuration—centrally controlled and adjustable at any time.
How easy is the integration?
Setup is performed entirely within the Microsoft Intune Admin Center and requires no changes to the Flexopus configuration. Administrators add the Flexopus app from the iOS App Store to Intune and then create an app configuration policy with the domain key. Once the policy is active, the configuration is automatically pushed to all managed devices.
A complete step-by-step guide for setup can be found in our Help Center.
What are the benefits of the integration?
- No manual domain entry: Users are automatically redirected to the Microsoft login page upon app launch—the domain is already pre-filled.
- Centralized app management: The Flexopus app is distributed directly via Intune to all managed devices—without employee intervention.
- Faster onboarding: New users can use Flexopus immediately after device registration.
- Fewer errors: Automatic configuration prevents typos during domain entry and the resulting login issues.
- Compatible with iOS and Android: The configuration policy is created for iOS and, thanks to the Intune architecture, also applies to Android devices.
- Included free in Flexopus subscription: The Intune integration is part of the standard Flexopus scope and incurs no additional costs.
Additional integrations
Questions and answers
Does the Intune configuration also need to be created separately for Android devices?
No. It is sufficient to create the configuration policy for iOS/iPadOS. Intune also applies the configuration to managed Android devices without requiring a separate policy.
What happens if the policy is not configured correctly?
If the configuration key "domain" is missing or the policy name is not exactly "FlexopusIntuneConfig", the domain will not be transferred automatically. In this case, the user will continue to see the manual domain input field. Administrators should check the configuration policy in the Intune Admin Center for completeness and correct spelling.
What data is transmitted to Flexopus via the Intune integration?
Only the domain value required to identify the correct corporate tenant. No personal user data or device information is transmitted to Flexopus via this configuration policy.
Can the integration also be used for devices that are not fully managed by Intune (BYOD)?
Automatic domain pre-filling only works on devices registered as "Managed Devices" in Intune. On private devices without full MDM management, users must continue to enter the domain manually.

