What it does
The native Android and iOS GoBright app integrates the Microsoft Intune App SDK. On a device, signing in via Sign in with Microsoft, or signing in with a Microsoft account via the email field, authenticates the user with Microsoft Entra ID and obtains the GoBright API token. When Intune is enabled for the GoBright relation, the app requires the Microsoft sign-in and registers the app account with Intune MAM before opening the app. Intune can then apply the App Protection Policy assigned to that user and app.
When an enrolled user logs out, the app asks for confirmation, clears the GoBright session data, and deregisters the account from Intune MAM.
This is mobile application management (MAM), not device enrollment. It protects work data in the GoBright app; it does not enroll or manage the whole phone, create Intune policies, or configure Conditional Access.
What problem it solves
Intune App Protection Policies let an organization protect its data on supported mobile platforms, including devices that are not enrolled in a mobile-device-management (MDM) solution. Depending on the policy and platform, controls can include restricting copy/paste or saving work data to personal locations, requiring an app PIN, encrypting work data, and blocking access based on device conditions.
This helps reduce data leakage from a work app without requiring full device management. The exact controls available depend on the operating system, and Intune policy. Conditional Access can be added separately when an organization wants Entra to require a protected app for access.
Configure GoBright
Please follow the step below to start configuring from GoBright side:
1. In the GoBright Admin Center, open Integrations and edit the organization's Office 365 integration.
2. In the Intune (beta) section, use Grant admin consent. Complete the Microsoft consent prompt in the same tenant using an administrator who can grant tenant-wide consent. The request is for GoBright's Intune integration to access the Intune MAM service (DeviceManagementManagedApps.ReadWrite).
3. Return to the integration, enable Enabled under Intune, and save it.
The Intune section is shown only for an Office 365 integration with a successful Modern Authentication tenant check and when GoBright's GeneralIntuneEnabled feature flag is enabled for the relation. If the section is missing, ask GoBright to check the feature flag and tenant connection.
Enabling this setting makes the mobile app require Microsoft sign-in and MAM registration for users in that GoBright relation. It does not create or assign an Intune App Protection Policy.
Configure Microsoft Entra and Intune
To complete the integration configuration, the following actions will need to be carried out on the Microsoft side:
1. Microsoft Entra
1.1 Grant consent from the Grant admin consent link in the GoBright integration. Use the correct Microsoft tenant and an administrator authorized to grant consent. Do not create a replacement app registration or change the GoBright app's redirect URIs; GoBright owns those app registrations.
1.2 Assign an Intune user license to each user who will receive an App Protection Policy. A user license is required even when their device is not enrolled in Intune.
1.3 Optional — Conditional Access: If your organization requires protected apps for access, create a Conditional Access policy for the appropriate users, GoBright resource, and iOS/Android platforms with Require app protection policy. Start in report-only mode, exclude emergency access accounts, and enforce the policy only after the Intune policy is assigned and tested. Conditional Access is separate from the GoBright Intune switch.
2. Microsoft Intune
2.1 Make sure users have the required broker app installed: Company Portal on Android and, when prompted for iOS sign-in, Microsoft Authenticator.
2.2 In the Microsoft Intune admin center, go to Apps > Protection > Create policy. Create a policy for Android and another for iOS/iPadOS.
2.3 On each policy's Apps page, target the GoBright mobile app. If GoBright is not available in the public-app list, use Selected apps and add it as a custom app. The current Android package ID and iOS bundle ID are both com.gobright.brightbooking.
2.4 Configure the organization's required Data protection, Access requirements, and Conditional launch settings. For example, choose the permitted data-transfer destinations and whether an app PIN or device conditions are required.
2.5 Assign the policy to the user groups that use GoBright mobile app, then create the policy. Policy assignment must include both the user and the GoBright app for it to apply.
MAM policies can protect the app without enrolling the device in MDM. A separate device-compliance or enrolment requirement in your Conditional Access policy may still require device registration or management.