Secure & Manage Content – UEM Authority https://guides.uemauthority.com Learn. Test. Deploy Thu, 20 Jan 2022 16:23:55 +0000 en-GB hourly 1 https://wordpress.org/?v=6.5.3 https://guides.uemauthority.com/wp-content/uploads/2021/11/cropped-UEM_Authority_Logo_favicon-32x32.png Secure & Manage Content – UEM Authority https://guides.uemauthority.com 32 32 214635633 Create an App Protection Policy (MAM) https://guides.uemauthority.com/knowledge-base/create-an-app-protection-policy-mam/?utm_source=rss&utm_medium=rss&utm_campaign=create-an-app-protection-policy-mam https://guides.uemauthority.com/knowledge-base/create-an-app-protection-policy-mam/#respond Thu, 20 Jan 2022 12:19:24 +0000 http://guides.uemauthority.com/?post_type=ht_kb&p=969 In this guide, we create an App Protection policy in order to demonstrate how to extend Data Protection and Data Loss Prevention (DLP) controls out to our managed and unmanaged devices.

App Protection for unmanaged devices is known as MAM without enrolment (MAM-WE). MAM-WE is commonly used for personal or bring your own devices (BYOD). Or, use on organisation-owned devices that need specific app configuration, or extra app security.

MAM-WE is also an option for users who don’t enroll their personal devices, but still need access to organisation email.

Create an App Protection Policy

Note – Outlook MAM protection requires an Azure AD account (Hybrid or Cloud) and Exchange Online mailbox (Hybrid or Cloud)

From the home dashboard, navigate to Apps > App Protection Policies.

Select the ‘Add’ button and then select ‘iOS/iPadOS’.

Set a Name and Description.
**Example**
Name: iOS – MAM Policy
Description: MAM Policy for iOS devices.

Select ‘Next’.

For the purposes of this training course, MAM will be targeted to both Managed and Unmanaged iOS devices.

The following App Protection settings will be set:
**Example**
Target to apps on all device types: Yes

Press ‘Select Public Apps’ and then select Outlook from the list.

Select ‘Next’.

Data Transfer

  • Backup org data to iTunes and iCloud backups: Block
  • Send org data to other apps: Policy managed apps
  • Select apps to exempt: Default
  • Save copies of org data: Block
  • Allow user to save copies to select services: OneDrive for Business & SharePoint
  • Transfer telecommunication data to: Any dialer app
  • Dialer App URL Scheme: None
  • Receive data from other apps: Policy managed apps
  • Open data into Org documents: Block
  • Allow to user open data from select services: OneDrive for Business, SharePoint & Camera
  • Restrict cut, copy, and paste between other apps: Policy managed apps
  • Cut and copy character limit for any app: 0
  • Third-party keyboards: Allow

Encryption

  • Encrypt org data: Require

Functionality

  • Sync policy managed app data with native apps: Allow
  • Printing org data: Block
  • Restrict web content transfer with other apps: Microsoft Edge
  • Unmanaged browser protocol: None
  • Org data notifications: Allow

Access Requirements

  • Pin for Acces: Not Required
  • Work or school account credentials for access: Not Required
  • Recheck the access requirements after (minutes of inactivity): 30

Conditional Launch

  • Offline grace period: 720 – Block access (minutes)
  • Offline grace period: 90 – Wipe data (days)
  • Jailbroken/Rooted devices: Block access

Select ‘Next’.

Under Assignments, select ‘Add Groups’.

In this example, the ‘Corporate Devices’ group will be selected.

Select ‘Select’ to add your Azure AD Group.

Select ‘Next’ and then ‘Create’.

Once created, you will see the App Protection Policy appear in the list ready for use.

See in Action

App Protection can be validated on the device by the user. Observing our enroled device in Outlook, we can test cut, copy and paste restrictions that are being enforced by our App Protection policy.

For the purposes of this demonstration, we have received an email from our fictional organisation that contains sensitive information. We will attempt to exfiltrate this information by means of Copy and Paste.

Copying text from the body of the email, we close Outlook and then open the native Notes app. Attempting to paste the copied information, App Protection replaces the original text in the clipboard cache with “Your orginastion’s data cannot be pasted here”.

Within the Endpoint Manager portal, we can validate which apps App Protection is applied to by app or user. Navigating to Apps > Monitor > App Protection Status > Reports.

Selecting the User Report, we choose the enroled user – johndoe@traininguemauthority.onmicrosoft.com.

The report shows iOS – MAM Policy is successfully applied against Microsoft Outlook.

]]>
https://guides.uemauthority.com/knowledge-base/create-an-app-protection-policy-mam/feed/ 0 969
Create an App Configuration Policy https://guides.uemauthority.com/knowledge-base/create-an-app-configuration-policy/?utm_source=rss&utm_medium=rss&utm_campaign=create-an-app-configuration-policy https://guides.uemauthority.com/knowledge-base/create-an-app-configuration-policy/#respond Thu, 20 Jan 2022 12:04:33 +0000 http://guides.uemauthority.com/?post_type=ht_kb&p=962 In this guide, we create an App Configuration policy in order to demonstrate how to pre-provision the Outlook app.

App Configuration is a way to streamline, and somewhat automate (to a degree), setup of work deployed/managed apps, to ensure employees are productive within minutes.

Create an App Configuration Policy

Note – Save Contacts settings refers to the enablement of Outlook Contacts and Calendar synchronization with your respective Native contacts and calendar apps. At present, only contacts sync is supported with Outlook for iOS. Outlook for Andoird supports both contacts and calendar sync. Refer to Microsoft documentation for further guidance.

Important – Outlook for Android supports bi-directional contact synchronization. However, if a user edits a field in the native contacts app that is restricted (such as the Notes field), then that data will not synchronize back into Outlook for Android.

From the home dashboard, navigate to Apps > App Configuration Policies.

Select the ‘Add’ button and then select ‘Managed Devices’.

Set a Name and Description.
**Example**
Name: iOS – Outlook App Configuration Policy
Description: App Configuration policy for Outlook on iOS.

Select iOS/iPadOS from the Platform dropdown.

Press the ‘Select app’ button, select Outlook from the list and then press ‘Ok’.

Select ‘Next’.

Select ‘Use Configuration Designer’ from the Configuration Settings Format dropdown.

For the purposes of this training course, the following Outlook App Configuration settings will be set:
**Example**
Email Account Configuration

  • Configure email account settings: Yes
  • Authentication type: Basic authentication
  • Username attribute from AAD: User Principal Name
  • Email address attribute from AAD: Primary SMTP Address
  • Email Server: outlook.office365.com
  • Email Account Name: Corporate Email

General App Configuration

  • Focused Inbox: On
  • Require Biometrics to access app: Off
  • Save Contacts: On
  • Allow user to change settings: Yes
  • Default app signature: On

Select ‘Next’.

Under Assignments, select ‘Add Groups’.

In this example, the ‘Corporate Devices’ group will be selected.

Select ‘Select’ to add your Azure AD Group.

Select ‘Next’ and then ‘Create’.

Once created, you will see the App Configuration Policy appear in the list ready for use.

See in Action

App Configuration can be enabled and validated on the device by the user. Observing our enroled device in Outlook, we can see App Configuration has detected and pre-populated our enroled user account – johndoe@traininguemauthority.onmicrosoft.com

After selecting ‘Add Account’, we sign in to complete authentication.

Within the Endpoint Manager portal, we can validate the App Configuration policy has been successfully installed on the device by navigating to Devices > All Devices.

Selecting the device entry, under App Configuration on the left side menu, we can see the App Configuration policy we created successfully installed.

]]>
https://guides.uemauthority.com/knowledge-base/create-an-app-configuration-policy/feed/ 0 962
Create an iOS Native Mail Profile https://guides.uemauthority.com/knowledge-base/create-an-ios-native-mail-profile/?utm_source=rss&utm_medium=rss&utm_campaign=create-an-ios-native-mail-profile https://guides.uemauthority.com/knowledge-base/create-an-ios-native-mail-profile/#respond Wed, 19 Jan 2022 16:53:20 +0000 http://guides.uemauthority.com/?post_type=ht_kb&p=954 In this guide, we create an iOS Email Profile which will be used to pre-provision the iOS native mail app with our test user account UPN and security type.

Create an iOS Email Profile

Note – The email profile uses the native or built-in email app on the device, and allows users to connect to their work email. This profile will not apply settings for Outlook mobile app.

From the home dashboard, navigate to Devices > Configuration Profiles.

Select the ‘Create Profile’ button.

Select ‘iOS/iPadOS’ as the platform.

Select ‘Email’ as the Profile Type and then select ‘Create’.

Set a Name and Description.
**Example**
Name: iOS – Email Profile
Description: Email profile for iOS devices.

Select ‘Next’

For the purposes of this training course, the following example email profile settings will be set:
**Example**
Exchange ActiveSync account settings

  • Email server: outlook.office365.com
  • Account name: Work Email
  • Username attribute from AAD: User Principal Name
  • Email address attribute from AAD: Primary SMTP Address
  • Authentication method: Username and password
  • SSL: Enable

Exchange ActiveSync profile configuration

  • Exchange data to sync: All data

Select ‘Next’.

Under Assignments, select ‘Add Groups’.

In this example, the ‘Corporate Devices’ group will be selected.

Select ‘Select’ to add your Azure AD Group.

Select ‘Next’ and then ‘Create’.

Once created, you will see the email profile appear in the list ready for use.

See in Action

Note – Device prompts and their wording may change and present slightly different between iOS versions.

Once the email profile has been successfully installed, the device will automatically prompt the user to complete Exchange ActiveSync authentication by asking for a password.

After authentication is complete, within the settings app under Mail > Accounts, we can see our account listed. Drilling down further into detail by selecting the email profile, we can validate the details match the Endpoint Manager deployed email profile.

Moving over to the native mail app, a test email has been received successfully.

Within the Endpoint Manager portal, we can validate the email profile has been successfully installed on the device by navigating to Devices > All Devices.

Selecting the device entry, under Device Configuration on the left side menu, we can see the email profile we created successfully installed.

]]>
https://guides.uemauthority.com/knowledge-base/create-an-ios-native-mail-profile/feed/ 0 954
Create an iOS Configuration Profile https://guides.uemauthority.com/knowledge-base/create-an-ios-configuration-profile/?utm_source=rss&utm_medium=rss&utm_campaign=create-an-ios-configuration-profile https://guides.uemauthority.com/knowledge-base/create-an-ios-configuration-profile/#respond Wed, 19 Jan 2022 16:09:42 +0000 http://guides.uemauthority.com/?post_type=ht_kb&p=950 In this guide, we create an iOS Configuration Profile using the Restrictions profile type in order to define baseline security and device password requirements.

Create an iOS Configuration Profile

Note – Apple iOS/iPadOS supervised mode gives administrators more options when managing Apple devices, making it useful for corporate-owned devices deployed at scale. For example, you can restrict AirDrop or prevent users from changing the name of the device. For a list of settings that require supervised mode, see iOS device restriction settings in Intune.

From the home dashboard, navigate to Devices > Configuration Profiles.

Select the ‘Create Profile’ button.

Select ‘iOS/iPadOS’ as the platform.

Select ‘Device Restrictions’ as the Profile Type and then select ‘Create’.

Set a Name and Description.
**Example**
Name: iOS – Device Restrictions Profile
Description: Device Restrictions profile for iOS devices.

Select ‘Next’

For the purposes of this training course, the following example baseline configuration profile settings will be tailored to an Unsupervised device:
**Example**
App Store, Doc Viewing, Gaming

  • Treat AirDrop as an unmanaged destination: Yes

Cloud and Storage

  • Force encrypted backup: Yes

Password

  • Require password: Yes
  • Block simple passwords: Yes
  • Required password type: Numeric
  • Number of non-alphanumeric characters in password: 1
  • Minimum password length: 6
  • Maximum minutes after screen lock before the password is required: Immediately
  • Maximum minutes of inactivity until screen locks: 5 minutes

Show or Hide Apps

  • Type of apps list: Hidden apps
  • Apps list: (Microsoft kindly provide a list of known Apple native app bundle ID’s)
    • App bundle ID: com.apple.gamecenter
    • App Name: Game Center

Wireless

  • Block data roaming: Yes

Select ‘Next’.

Under Assignments, select ‘Add Groups’.

In this example, the ‘Corporate Devices’ group will be selected.

Select ‘Select’ to add your Azure AD Group.

Select ‘Next’ and then ‘Create’.

Once created, you will see the configuration profile appear in the list ready for use.

See in Action

Installed configuration can be validated on the device by the user. Observing our enrolled device with the setting app, under General > Device Management > Management Profile, we can see “2 Restrictions” and “Password Policy” listed in the Contains list.

Selecting Restrictions, we can further validate device restriction settings match the Endpoint Manager deployed configuration profile we created.

Drilling down into more detail by selecting the password policy, again, we can validate the password policy being enforced on the device matches the Endpoint Manager deployed configuration profile.

Within the Endpoint Manager portal, we can validate the configuration profile has been successfully installed on the device by navigating to Devices > All Devices.

Selecting the device entry, under Device Configuration on the left side menu, we can see the configuration profile we created successfully installed.

]]>
https://guides.uemauthority.com/knowledge-base/create-an-ios-configuration-profile/feed/ 0 950
Create an iOS Compliance Policy https://guides.uemauthority.com/knowledge-base/create-an-ios-compliance-policy/?utm_source=rss&utm_medium=rss&utm_campaign=create-an-ios-compliance-policy https://guides.uemauthority.com/knowledge-base/create-an-ios-compliance-policy/#respond Wed, 19 Jan 2022 16:01:26 +0000 http://guides.uemauthority.com/?post_type=ht_kb&p=948 In this guide, we create an iOS Compliance Policy in order to define a baseline compliance criteria that devices, to be managed by Intune, must meet.

Create an iOS Compliance Policy

Note – Compliance requires users and devices to meet criteria set by an organisation. Rules and settings are defined which Endpoint Manager compliance engine will assess users and against to determine their respective compliance status. Compliance does not configure the device.

Sign in to your Endpoint Manager portal by browsing to https://endpoint.microsoft.com
From the home dashboard, navigate to Devices > Compliance Policies.

Select the ‘Create Policy’ button.

Select ‘iOS/iPadOS’ as the platform and then select ‘Create’.

Set a Name and Description.
**Example**
Name: iOS – Compliance Policy
Description: Compliance policy for iOS devices.

Select ‘Next’

For the purposes of this training course, the following example baseline compliance settings will be set:
**Example**
Email

  • Unable to set up email on the device: Require

Device Health

  • Jailbroken devices: Block
  • Require the device to be at or under the Device Threat Level: Not Configured

Device Properties

  • Minimum OS version: 13.0
  • Microsoft Defender for Endpoint: Not Configured

System Security

  • Require a password to unlock mobile devices: Require
  • Simple passwords: Block

Minimum password length: 6

  • Required password type: Numeric
  • Number of non-alphanumeric characters in password: 1
  • Maximum minutes after screen lock before the password is required: Immediately
  • Maximum minutes of inactivity until screen locks: 5 minutes

Select ‘Next’.
Actions for non-compliance will remain unchanged.

Select ‘Next’.

Under Assignments, select ‘Add Groups’.

In this example, the ‘Corporate Devices’ group will be selected.

Select ‘Select’ to add your Azure AD Group.

Select ‘Next’ and then ‘Create’.

Once created, you will see the compliance policy appear in the list ready for use.

See in Action

Device compliance status can be validated on the device by the user. Observing our enrolled device within the Company Portal app, we can see the status says “Can access company resources”.

Within the Endpoint Manager portal, we can validate the compliance status of a device by navigating to Devices > All Devices.

Observing the device in question, we can see the compliance column indicates the device is compliant.

Selecting the device entry, under Device Compliance on the left side menu, we can see the compliance policy we created successfully assessed the device.

]]>
https://guides.uemauthority.com/knowledge-base/create-an-ios-compliance-policy/feed/ 0 948